Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 592f24aa5d16783dd835d4504351daa2ed80c15a975dc30c3551fc2a910d4484

Tx prefix hash: 643232b68222e1b91ec813743c21298deacea4458eac7a4520ec5014a1b5f500
Tx public key: 08ce819f085cbf4a821d620779b1d1f6d0adf2532e199eff726899faff1c6b14
Timestamp: 1737832528 Timestamp [UCT]: 2025-01-25 19:15:28 Age [y:d:h:m:s]: 00:144:05:26:17
Block: 1205202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102806 RingCT/type: yes/0
Extra: 0108ce819f085cbf4a821d620779b1d1f6d0adf2532e199eff726899faff1c6b140211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3c6d7334c4f79dddf23b526e592d3e77f2cb1d8682ba8d84e56c903832117f5 0.600000000000 1691899 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": 1205212, "vin": [ { "gen": { "height": 1205202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3c6d7334c4f79dddf23b526e592d3e77f2cb1d8682ba8d84e56c903832117f5" } } ], "extra": [ 1, 8, 206, 129, 159, 8, 92, 191, 74, 130, 29, 98, 7, 121, 177, 209, 246, 208, 173, 242, 83, 46, 25, 158, 255, 114, 104, 153, 250, 255, 28, 107, 20, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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