Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f49dc1baa71423fbebf17b458f71de43d32752abe6c2b50fc575b77582a00d23

Tx prefix hash: 4530ad948726e5e52d1848cc86a7b841d3f15723d390aa159ed5d8c25592c149
Tx public key: f0e3eab9d47a90d469a79240a5e0b6e78e088a2bf7661a194417e1a412d9b170
Timestamp: 1764146541 Timestamp [UCT]: 2025-11-26 08:42:21 Age [y:d:h:m:s]: 00:000:23:12:36
Block: 1420417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 701 RingCT/type: yes/0
Extra: 01f0e3eab9d47a90d469a79240a5e0b6e78e088a2bf7661a194417e1a412d9b1700211000000024e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4179a304c03a8bf4946041df6c166cc50c4a25f76bcf9ef7bc2aa87a8478188 0.600000000000 1908960 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": 1420427, "vin": [ { "gen": { "height": 1420417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4179a304c03a8bf4946041df6c166cc50c4a25f76bcf9ef7bc2aa87a8478188" } } ], "extra": [ 1, 240, 227, 234, 185, 212, 122, 144, 212, 105, 167, 146, 64, 165, 224, 182, 231, 142, 8, 138, 43, 247, 102, 26, 25, 68, 23, 225, 164, 18, 217, 177, 112, 2, 17, 0, 0, 0, 2, 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