Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94f205f71d0c851c22e03d6ea72bd0b70e4706acd8ee8c6daf4d4923bef2daf6

Tx prefix hash: 2f315037fbbd47404de74ab836551742a1e0fb33a997e714faf8fdde3798d994
Tx public key: c33c0867199f890b3ba4628b240526f891a81dbd3d3af822e08594f1b83bc664
Timestamp: 1682316803 Timestamp [UCT]: 2023-04-24 06:13:23 Age [y:d:h:m:s]: 01:350:08:13:53
Block: 745387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511652 RingCT/type: yes/0
Extra: 01c33c0867199f890b3ba4628b240526f891a81dbd3d3af822e08594f1b83bc664021100000001b3164c24000000000000000000

1 output(s) for total of 2.080767970000 dcy

stealth address amount amount idx
00: 57185c9e909873ef0ff38bfff084ab48ea7c3fc1a4a029d6cc802fda075e443b 2.080767970000 1192834 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": 745397, "vin": [ { "gen": { "height": 745387 } } ], "vout": [ { "amount": 2080767970, "target": { "key": "57185c9e909873ef0ff38bfff084ab48ea7c3fc1a4a029d6cc802fda075e443b" } } ], "extra": [ 1, 195, 60, 8, 103, 25, 159, 137, 11, 59, 164, 98, 139, 36, 5, 38, 248, 145, 168, 29, 189, 61, 58, 248, 34, 224, 133, 148, 241, 184, 59, 198, 100, 2, 17, 0, 0, 0, 1, 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