Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be6de37df4f6596c64fefd201bb697d24e303c2768031937050086633c4693d1

Tx prefix hash: 60275f55b1a17044aa322eacbb78663c239746617452801cf2a076d9039fbcd7
Tx public key: 60ad3a3e01e2e891a5d9a7a255119b637a243ab37f0a55480312ce0f91a84805
Timestamp: 1658527662 Timestamp [UCT]: 2022-07-22 22:07:42 Age [y:d:h:m:s]: 02:158:13:22:21
Block: 549551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 634714 RingCT/type: yes/0
Extra: 0160ad3a3e01e2e891a5d9a7a255119b637a243ab37f0a55480312ce0f91a84805021100000004cb8520c2000000000000000000

1 output(s) for total of 9.270636237000 dcy

stealth address amount amount idx
00: f21a23b09a5daf3b591ce6f373ca484c6fc93482d8a07674ef71e7dd5596ad45 9.270636237000 980928 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": 549561, "vin": [ { "gen": { "height": 549551 } } ], "vout": [ { "amount": 9270636237, "target": { "key": "f21a23b09a5daf3b591ce6f373ca484c6fc93482d8a07674ef71e7dd5596ad45" } } ], "extra": [ 1, 96, 173, 58, 62, 1, 226, 232, 145, 165, 217, 167, 162, 85, 17, 155, 99, 122, 36, 58, 179, 127, 10, 85, 72, 3, 18, 206, 15, 145, 168, 72, 5, 2, 17, 0, 0, 0, 4, 203, 133, 32, 194, 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