Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c452bfccd92648c9c47c6204bd51c53a6a26636b94dd91b4139650e297f40491

Tx prefix hash: 84e0b599c866788f043d13adf6feabf67956d3b43036ddbc9fdc186d76b37d0c
Tx public key: afacd9baf115482c2be4df3ee30015da3dbab430520b4aa506b581143d8fa0c2
Timestamp: 1685474443 Timestamp [UCT]: 2023-05-30 19:20:43 Age [y:d:h:m:s]: 01:364:07:17:34
Block: 771579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521603 RingCT/type: yes/0
Extra: 01afacd9baf115482c2be4df3ee30015da3dbab430520b4aa506b581143d8fa0c2021100000002b3164c24000000000000000000

1 output(s) for total of 1.703878594000 dcy

stealth address amount amount idx
00: 8137f45c205451b0834051f00d6491b1fd76eabd7a881d69443d2ea87cd9ce1d 1.703878594000 1220952 of 0

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": 771589, "vin": [ { "gen": { "height": 771579 } } ], "vout": [ { "amount": 1703878594, "target": { "key": "8137f45c205451b0834051f00d6491b1fd76eabd7a881d69443d2ea87cd9ce1d" } } ], "extra": [ 1, 175, 172, 217, 186, 241, 21, 72, 44, 43, 228, 223, 62, 227, 0, 21, 218, 61, 186, 180, 48, 82, 11, 74, 165, 6, 181, 129, 20, 61, 143, 160, 194, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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