Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74efb97fa36b5e19ee407878783c2db63438ef5ea239b2b2c5c490ecec19d545

Tx prefix hash: 08e56edd228e5b70f77c869e0c664e8bfc0b3d68b813ad292e9500061e7b341b
Tx public key: bac09cf5458bddd831c52834e6ce585f728b90c36ebad282f82746d1ed97d0a6
Timestamp: 1700920362 Timestamp [UCT]: 2023-11-25 13:52:42 Age [y:d:h:m:s]: 01:204:00:23:08
Block: 899383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406902 RingCT/type: yes/0
Extra: 01bac09cf5458bddd831c52834e6ce585f728b90c36ebad282f82746d1ed97d0a60211000000014b8f5122000000000000000000

1 output(s) for total of 0.642644439000 dcy

stealth address amount amount idx
00: 099c6588b790d7e29ea52288b3708bb59e0ac96f59186684faa1ef7cb2d27547 0.642644439000 1355836 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": 899393, "vin": [ { "gen": { "height": 899383 } } ], "vout": [ { "amount": 642644439, "target": { "key": "099c6588b790d7e29ea52288b3708bb59e0ac96f59186684faa1ef7cb2d27547" } } ], "extra": [ 1, 186, 192, 156, 245, 69, 139, 221, 216, 49, 197, 40, 52, 230, 206, 88, 95, 114, 139, 144, 195, 110, 186, 210, 130, 248, 39, 70, 209, 237, 151, 208, 166, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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