Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fa170ba6cc3d8b146bd5a427b2108794578b4347c18ce4b6485dfe25a81eadc

Tx prefix hash: 74a019997e6d34e82d420023689e0fd8953df690cf03c8df37fd0bf2af2f5a31
Tx public key: a4b0ffb063519080478b410ce03396f6f53002f58c29a1488ee1d45291b1d675
Timestamp: 1748764309 Timestamp [UCT]: 2025-06-01 07:51:49 Age [y:d:h:m:s]: 00:169:15:56:54
Block: 1295496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118932 RingCT/type: yes/0
Extra: 01a4b0ffb063519080478b410ce03396f6f53002f58c29a1488ee1d45291b1d675021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8432fb8a15c86f6364813f7d5f9a0373af8ea84b0af752e29eba91f848df0402 0.600000000000 1782999 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": 1295506, "vin": [ { "gen": { "height": 1295496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8432fb8a15c86f6364813f7d5f9a0373af8ea84b0af752e29eba91f848df0402" } } ], "extra": [ 1, 164, 176, 255, 176, 99, 81, 144, 128, 71, 139, 65, 12, 224, 51, 150, 246, 245, 48, 2, 245, 140, 41, 161, 72, 142, 225, 212, 82, 145, 177, 214, 117, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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