Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36e93debbbf40b3b0ed52ae04280efe86dff596d4f781b99628b7e27d338f919

Tx prefix hash: 4f71686d7d65a227a63ca55242151b19de0217c112f817c4b6951e227a5d6b39
Tx public key: 4339e92ad01ee451d80209e3b1ee0444b1cfab514f94ab34159f63dc26f18684
Timestamp: 1756008037 Timestamp [UCT]: 2025-08-24 04:00:37 Age [y:d:h:m:s]: 00:077:20:25:58
Block: 1353156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55564 RingCT/type: yes/0
Extra: 014339e92ad01ee451d80209e3b1ee0444b1cfab514f94ab34159f63dc26f186840211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd854031765aa02a1c92c599b8f445e9a0093b3ec313efa32d786f2caac2f7d2 0.600000000000 1841129 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": 1353166, "vin": [ { "gen": { "height": 1353156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd854031765aa02a1c92c599b8f445e9a0093b3ec313efa32d786f2caac2f7d2" } } ], "extra": [ 1, 67, 57, 233, 42, 208, 30, 228, 81, 216, 2, 9, 227, 177, 238, 4, 68, 177, 207, 171, 81, 79, 148, 171, 52, 21, 159, 99, 220, 38, 241, 134, 132, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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