Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0e0e0d8338c447d871df1ee56ace3663a248ac47ab8d8bdcf0dad4bf961c8ea

Tx prefix hash: 980bbbef86ff71ebdef423f6eb913a63c9e6982f7f38a9fdc06f1e09b2d18d69
Tx public key: 7e62c088c7c6db781fc5493d594298505b9c07a4fa747580162c2073b7efa17d
Timestamp: 1577644124 Timestamp [UCT]: 2019-12-29 18:28:44 Age [y:d:h:m:s]: 05:093:03:19:02
Block: 34480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1216343 RingCT/type: yes/0
Extra: 017e62c088c7c6db781fc5493d594298505b9c07a4fa747580162c2073b7efa17d0211000000024ac5aa02000000000000000000

1 output(s) for total of 471.796052015000 dcy

stealth address amount amount idx
00: 79ba625b82eeef9949b836f939afdf6e357576a65f7a4a2b743ff88304f50ff0 471.796052015000 58030 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": 34490, "vin": [ { "gen": { "height": 34480 } } ], "vout": [ { "amount": 471796052015, "target": { "key": "79ba625b82eeef9949b836f939afdf6e357576a65f7a4a2b743ff88304f50ff0" } } ], "extra": [ 1, 126, 98, 192, 136, 199, 198, 219, 120, 31, 197, 73, 61, 89, 66, 152, 80, 91, 156, 7, 164, 250, 116, 117, 128, 22, 44, 32, 115, 183, 239, 161, 125, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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