Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0668e5784dca67a1e1bca2d6f7a7da18b16f1262447ae151cf9e77d94e00b150

Tx prefix hash: 23b5da7d6a81fb1eb55fbad2c9e4f6120a74281bf5d0dc18519f367eb0ca5ee0
Tx public key: 678735f050bab1635202f46d7f8fc621607326dd15c9d318579aa5de9adac9e2
Timestamp: 1675385382 Timestamp [UCT]: 2023-02-03 00:49:42 Age [y:d:h:m:s]: 02:074:05:47:47
Block: 688556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 574689 RingCT/type: yes/0
Extra: 01678735f050bab1635202f46d7f8fc621607326dd15c9d318579aa5de9adac9e20211000000015029cbac000000000000000000

1 output(s) for total of 3.210170274000 dcy

stealth address amount amount idx
00: 85f7047b8b38e7f0e85176dd15c2c618f412ef3b53c74b77c512d99efab819c8 3.210170274000 1131180 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": 688566, "vin": [ { "gen": { "height": 688556 } } ], "vout": [ { "amount": 3210170274, "target": { "key": "85f7047b8b38e7f0e85176dd15c2c618f412ef3b53c74b77c512d99efab819c8" } } ], "extra": [ 1, 103, 135, 53, 240, 80, 186, 177, 99, 82, 2, 244, 109, 127, 143, 198, 33, 96, 115, 38, 221, 21, 201, 211, 24, 87, 154, 165, 222, 154, 218, 201, 226, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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