Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 047c4e2e3b30aa1d1632f853e6acecd74f33e0984b4c82bd65ceaab3c8666303

Tx prefix hash: a79967b7bd2fafdf2657288c81234d6ba3980b1c4262dcb530fb979f4b29a5dd
Tx public key: 680ac30a0c8502ce9e0735e2fc76e35e5f1ef17060e64e25ab98798a2215422e
Timestamp: 1726543501 Timestamp [UCT]: 2024-09-17 03:25:01 Age [y:d:h:m:s]: 00:115:00:40:36
Block: 1111803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82254 RingCT/type: yes/0
Extra: 01680ac30a0c8502ce9e0735e2fc76e35e5f1ef17060e64e25ab98798a2215422e02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd510ae99a9306436f9c69d3e3e0eb1d9ab7585f091123ede53c51dfb0254caf 0.600000000000 1590892 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": 1111813, "vin": [ { "gen": { "height": 1111803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd510ae99a9306436f9c69d3e3e0eb1d9ab7585f091123ede53c51dfb0254caf" } } ], "extra": [ 1, 104, 10, 195, 10, 12, 133, 2, 206, 158, 7, 53, 226, 252, 118, 227, 94, 95, 30, 241, 112, 96, 230, 78, 37, 171, 152, 121, 138, 34, 21, 66, 46, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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