Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8b144e273a4f0baaba78a0f1c5376a5e717ac3037ad26210dbd9435c3dac1bb

Tx prefix hash: 79a20992608b43f79d0abd0260998e2b9feffcd856808130ebb8f99516a8ba45
Tx public key: 42530a78acc65f66177e2a6004786a9091b0662a341f1b8dc2e5430fa9b1e716
Timestamp: 1727997396 Timestamp [UCT]: 2024-10-03 23:16:36 Age [y:d:h:m:s]: 00:110:07:34:18
Block: 1123857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78827 RingCT/type: yes/0
Extra: 0142530a78acc65f66177e2a6004786a9091b0662a341f1b8dc2e5430fa9b1e71602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dec56db172a04385db2b2811eb8670a2aa456af629c853c3d95d1ee36a89a2c 0.600000000000 1606396 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": 1123867, "vin": [ { "gen": { "height": 1123857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dec56db172a04385db2b2811eb8670a2aa456af629c853c3d95d1ee36a89a2c" } } ], "extra": [ 1, 66, 83, 10, 120, 172, 198, 95, 102, 23, 126, 42, 96, 4, 120, 106, 144, 145, 176, 102, 42, 52, 31, 27, 141, 194, 229, 67, 15, 169, 177, 231, 22, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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