Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f856af22dc5d6953fcdab4c21576f4762cae86486a6c0cb280810133781f68f9

Tx prefix hash: 421f499b55d5a642e7ffa79c0fdad85f7b3073c84ad40f15d70052fbc533aa8b
Tx public key: 24fb28e8b610e8cbe4aa6140d1550f06ee9a7dcda359fa3dfed4df3824fdcbce
Timestamp: 1711190030 Timestamp [UCT]: 2024-03-23 10:33:50 Age [y:d:h:m:s]: 01:074:17:58:35
Block: 984539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314415 RingCT/type: yes/0
Extra: 0124fb28e8b610e8cbe4aa6140d1550f06ee9a7dcda359fa3dfed4df3824fdcbce0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b297d267fbd874fe7af27b7c78341d95d43b76c2fc56d07398ebaa21ea1fbd6b 0.600000000000 1444710 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": 984549, "vin": [ { "gen": { "height": 984539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b297d267fbd874fe7af27b7c78341d95d43b76c2fc56d07398ebaa21ea1fbd6b" } } ], "extra": [ 1, 36, 251, 40, 232, 182, 16, 232, 203, 228, 170, 97, 64, 209, 85, 15, 6, 238, 154, 125, 205, 163, 89, 250, 61, 254, 212, 223, 56, 36, 253, 203, 206, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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