Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9fb2bb65ad63954e4be2f0875db71302d3ed44c780f0c6a707f49036b61c986

Tx prefix hash: a678b1bd9e667a8ceccc303a2fb33c8d51ec1cffdd9ad86f35365a7819c4545b
Tx public key: 6b9063afbf7218e53e409ea6e296d1d1255e593769a7e2a164366404c975c40e
Timestamp: 1735473648 Timestamp [UCT]: 2024-12-29 12:00:48 Age [y:d:h:m:s]: 00:174:06:06:48
Block: 1185703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124220 RingCT/type: yes/0
Extra: 016b9063afbf7218e53e409ea6e296d1d1255e593769a7e2a164366404c975c40e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80bddceac6e9fc635b46eb63bc701d7bfb431ecfe0c9c214d2c15e651019c3be 0.600000000000 1672178 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": 1185713, "vin": [ { "gen": { "height": 1185703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80bddceac6e9fc635b46eb63bc701d7bfb431ecfe0c9c214d2c15e651019c3be" } } ], "extra": [ 1, 107, 144, 99, 175, 191, 114, 24, 229, 62, 64, 158, 166, 226, 150, 209, 209, 37, 94, 89, 55, 105, 167, 226, 161, 100, 54, 100, 4, 201, 117, 196, 14, 2, 17, 0, 0, 0, 3, 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