Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45e0acb8f0c5e13470ccb1cc16d730f82a51efc07e17c05f2dccb249cb253843

Tx prefix hash: 75fb8c006fee88fdcca3f7e499a5298cec52f901523f3beaaba651ad52cf349c
Tx public key: 76f823b3771ea861a6520e662cdf8dd1ecd412130ccc21f9a6f48a3d834f4b64
Timestamp: 1581245884 Timestamp [UCT]: 2020-02-09 10:58:04 Age [y:d:h:m:s]: 05:128:00:45:44
Block: 61263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1244246 RingCT/type: yes/0
Extra: 0176f823b3771ea861a6520e662cdf8dd1ecd412130ccc21f9a6f48a3d834f4b640211000000e70aca7173000000000000000000

1 output(s) for total of 384.601581725000 dcy

stealth address amount amount idx
00: ef8ec80f78647b1741d635a1aec318f6f07a796dc7cb131def16df59ac914e8d 384.601581725000 112893 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": 61273, "vin": [ { "gen": { "height": 61263 } } ], "vout": [ { "amount": 384601581725, "target": { "key": "ef8ec80f78647b1741d635a1aec318f6f07a796dc7cb131def16df59ac914e8d" } } ], "extra": [ 1, 118, 248, 35, 179, 119, 30, 168, 97, 166, 82, 14, 102, 44, 223, 141, 209, 236, 212, 18, 19, 12, 204, 33, 249, 166, 244, 138, 61, 131, 79, 75, 100, 2, 17, 0, 0, 0, 231, 10, 202, 113, 115, 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