Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 695e37ff7373701470cdd8030b6f347b973e19ee38a3bcf2adcc23656e3c76d0

Tx prefix hash: 14bd20e6304ddf9e4b0e92562b85111bd4f327c0a09a1088346ccf9d0ba06585
Tx public key: c3dc49a5173e3e5aa0546a0e09c2cf18e67b7c0ba7d8c4c1762dfbb15e7a1560
Timestamp: 1707368941 Timestamp [UCT]: 2024-02-08 05:09:01 Age [y:d:h:m:s]: 01:067:07:20:48
Block: 952831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309155 RingCT/type: yes/0
Extra: 01c3dc49a5173e3e5aa0546a0e09c2cf18e67b7c0ba7d8c4c1762dfbb15e7a15600211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53295f2927a306d72617a0359e9e4b6a741b25383a5d01bd616b34efd4a04649 0.600000000000 1411963 of 15

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": 952841, "vin": [ { "gen": { "height": 952831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53295f2927a306d72617a0359e9e4b6a741b25383a5d01bd616b34efd4a04649" } } ], "extra": [ 1, 195, 220, 73, 165, 23, 62, 62, 90, 160, 84, 106, 14, 9, 194, 207, 24, 230, 123, 124, 11, 167, 216, 196, 193, 118, 45, 251, 177, 94, 122, 21, 96, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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