Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18baec0310e107726fa2709012d8271c68baa26c274218f95e54ab5637dfa80b

Tx prefix hash: 3dd38052afac9dfc3db6b09d348814be661f5ed7a63bf356fad506f05883d60d
Tx public key: c38ddc63b5416c6bb5916c754274ac6751f905120edc7e1c2aa2953d0da2ae66
Timestamp: 1764142982 Timestamp [UCT]: 2025-11-26 07:43:02 Age [y:d:h:m:s]: 00:001:05:33:27
Block: 1420388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 888 RingCT/type: yes/0
Extra: 01c38ddc63b5416c6bb5916c754274ac6751f905120edc7e1c2aa2953d0da2ae660211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ba07caf0b2517854793b529fc3e59ba0b3ef9d15e75ea3d0e4b1f2496b718e2 0.600000000000 1908931 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": 1420398, "vin": [ { "gen": { "height": 1420388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ba07caf0b2517854793b529fc3e59ba0b3ef9d15e75ea3d0e4b1f2496b718e2" } } ], "extra": [ 1, 195, 141, 220, 99, 181, 65, 108, 107, 181, 145, 108, 117, 66, 116, 172, 103, 81, 249, 5, 18, 14, 220, 126, 28, 42, 162, 149, 61, 13, 162, 174, 102, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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