Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9651718bb80a937734a4872afbcfa8078960cf2eb6061cc797d734ac8f0c0ff

Tx prefix hash: 663e8b8f92fc1b3d656d44abdb1aed2bf94c057fc92434d4be867d37f855d56f
Tx public key: df583223c0511541f5d4cb3044f81983669eb6e8bf34a283c49ad00cc92a5102
Timestamp: 1697409210 Timestamp [UCT]: 2023-10-15 22:33:30 Age [y:d:h:m:s]: 01:213:02:33:30
Block: 870471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413353 RingCT/type: yes/0
Extra: 01df583223c0511541f5d4cb3044f81983669eb6e8bf34a283c49ad00cc92a510202110000000275e3f0e9000000000000000000

1 output(s) for total of 0.801250390000 dcy

stealth address amount amount idx
00: 365a75dcac33ad9b39545c8b1ff9ed13427cb215e4015489372811d4aeeb4ef8 0.801250390000 1325350 of 0

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": 870481, "vin": [ { "gen": { "height": 870471 } } ], "vout": [ { "amount": 801250390, "target": { "key": "365a75dcac33ad9b39545c8b1ff9ed13427cb215e4015489372811d4aeeb4ef8" } } ], "extra": [ 1, 223, 88, 50, 35, 192, 81, 21, 65, 245, 212, 203, 48, 68, 248, 25, 131, 102, 158, 182, 232, 191, 52, 162, 131, 196, 154, 208, 12, 201, 42, 81, 2, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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