Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5adcefebb38867089636dbb56a6fa632e5b9db744e461e7a61afe73c88c27dcf

Tx prefix hash: b3951ec8cdb30bf9de9a9a640933b9f6948e0226594b8e0c594e7e2895a79b8d
Tx public key: d3d2921fe8a9c82810495c26ff266a89fb9799ed2dbb9b50ef01dd55abf47f3b
Timestamp: 1709922859 Timestamp [UCT]: 2024-03-08 18:34:19 Age [y:d:h:m:s]: 01:080:00:21:03
Block: 974024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318205 RingCT/type: yes/0
Extra: 01d3d2921fe8a9c82810495c26ff266a89fb9799ed2dbb9b50ef01dd55abf47f3b02110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a12ff2ef8e4354231b68ac6a2ae969f7a220c699cd9877f087dc7e6985322cb 0.600000000000 1433967 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": 974034, "vin": [ { "gen": { "height": 974024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a12ff2ef8e4354231b68ac6a2ae969f7a220c699cd9877f087dc7e6985322cb" } } ], "extra": [ 1, 211, 210, 146, 31, 232, 169, 200, 40, 16, 73, 92, 38, 255, 38, 106, 137, 251, 151, 153, 237, 45, 187, 155, 80, 239, 1, 221, 85, 171, 244, 127, 59, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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