Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d8c1927434b0c6c37d67241f6ce51fa53b2038a35910fb86c611cc3b2cbed1f

Tx prefix hash: 2549676a3328440dfc03ff2aa59186f1b891ee168040faeb2080b7091765e063
Tx public key: b33ddc54850fbfe6acfa2da405e4e9a4181a1f1132afe99b9d53e6ed9729cdc8
Timestamp: 1716250020 Timestamp [UCT]: 2024-05-21 00:07:00 Age [y:d:h:m:s]: 00:333:10:49:43
Block: 1026471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238328 RingCT/type: yes/0
Extra: 01b33ddc54850fbfe6acfa2da405e4e9a4181a1f1132afe99b9d53e6ed9729cdc802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53b52f49e32a79225a09985dd99b16b5a3f029bd7555671633d3b455ba2d31ba 0.600000000000 1493574 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": 1026481, "vin": [ { "gen": { "height": 1026471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53b52f49e32a79225a09985dd99b16b5a3f029bd7555671633d3b455ba2d31ba" } } ], "extra": [ 1, 179, 61, 220, 84, 133, 15, 191, 230, 172, 250, 45, 164, 5, 228, 233, 164, 24, 26, 31, 17, 50, 175, 233, 155, 157, 83, 230, 237, 151, 41, 205, 200, 2, 17, 0, 0, 0, 1, 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