Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 21a640c3f033b9643d76d8b85ee0094dab9e1aa60ebe9197ae40449ba710bf65

Tx prefix hash: 572373f754a8f1dcb30430cae800c0f30e59d4da0b8b832757a8c4cf6ce1b5c6
Tx public key: 0496a2f427f58ea7380503eea6976f1ce11dc73545a53db3c5f0c8a73008540a
Timestamp: 1742265984 Timestamp [UCT]: 2025-03-18 02:46:24 Age [y:d:h:m:s]: 00:245:20:28:13
Block: 1241683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173442 RingCT/type: yes/0
Extra: 010496a2f427f58ea7380503eea6976f1ce11dc73545a53db3c5f0c8a73008540a021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a45d2c2fec6cb23520ad41ce277946531ba91e7059aadb5c97b774c8d5aaa57c 0.600000000000 1728656 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1241693, "vin": [ { "gen": { "height": 1241683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a45d2c2fec6cb23520ad41ce277946531ba91e7059aadb5c97b774c8d5aaa57c" } } ], "extra": [ 1, 4, 150, 162, 244, 39, 245, 142, 167, 56, 5, 3, 238, 166, 151, 111, 28, 225, 29, 199, 53, 69, 165, 61, 179, 197, 240, 200, 167, 48, 8, 84, 10, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8