Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21fb978d6af465de1bbe7a5e8a5aeea20c1c212bc624684d1db7664b64b184be

Tx prefix hash: 67fffa3533d1a1f242fb321cf8f1785c4972b0515dd2da6ce3ef3838aa616d22
Tx public key: 4a5e8e43e2b4b6bf7c24d92d0cbdea935d8c0b66c16bf8bfc571a257a553bd39
Timestamp: 1737011523 Timestamp [UCT]: 2025-01-16 07:12:03 Age [y:d:h:m:s]: 00:155:18:35:37
Block: 1198435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110995 RingCT/type: yes/0
Extra: 014a5e8e43e2b4b6bf7c24d92d0cbdea935d8c0b66c16bf8bfc571a257a553bd39021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe9a6c02fc60eab25a161c5cc8714fd6cc69028cc547f524d9034e5eded27672 0.600000000000 1685060 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": 1198445, "vin": [ { "gen": { "height": 1198435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe9a6c02fc60eab25a161c5cc8714fd6cc69028cc547f524d9034e5eded27672" } } ], "extra": [ 1, 74, 94, 142, 67, 226, 180, 182, 191, 124, 36, 217, 45, 12, 189, 234, 147, 93, 140, 11, 102, 193, 107, 248, 191, 197, 113, 162, 87, 165, 83, 189, 57, 2, 17, 0, 0, 0, 3, 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