Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da26de9f1a5871c2d39545e4ec6072f55360626f6e4ec700c7fd5d96be7a4756

Tx prefix hash: 692722332cbc4b45076f234ed5e0c32f5d4f69ec61d6fa17d94a85bab4dbbe94
Tx public key: dd062704f3d036c1550725e65afd8b1857077c931e35c3e40ec55b81c9bf1ea2
Timestamp: 1734216456 Timestamp [UCT]: 2024-12-14 22:47:36 Age [y:d:h:m:s]: 00:094:19:20:25
Block: 1175325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67541 RingCT/type: yes/0
Extra: 01dd062704f3d036c1550725e65afd8b1857077c931e35c3e40ec55b81c9bf1ea2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d044ba680760881f2c2e433279509c32e57af5eaa335f7439538008f3ea497b 0.600000000000 1661590 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": 1175335, "vin": [ { "gen": { "height": 1175325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d044ba680760881f2c2e433279509c32e57af5eaa335f7439538008f3ea497b" } } ], "extra": [ 1, 221, 6, 39, 4, 243, 208, 54, 193, 85, 7, 37, 230, 90, 253, 139, 24, 87, 7, 124, 147, 30, 53, 195, 228, 14, 197, 91, 129, 201, 191, 30, 162, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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