Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7893fc0eec56edf0139f3bf5e0c239f3ed57eb7b651a051ffa65eddb86943cf

Tx prefix hash: c019ff2403b944d155cb67d767356423e86623f67164a28234e1e3af13466102
Tx public key: 574775fde3a85f81a504b667b861ca8b52c3cbcf41542ea77bb089d61cdc2fb1
Timestamp: 1732696693 Timestamp [UCT]: 2024-11-27 08:38:13 Age [y:d:h:m:s]: 00:168:21:36:00
Block: 1162722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120548 RingCT/type: yes/0
Extra: 01574775fde3a85f81a504b667b861ca8b52c3cbcf41542ea77bb089d61cdc2fb1021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b17b59a1b544e8e904cc5b271696a72afe77a6d201a3326fc4e33a952f8fcfd 0.600000000000 1648379 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": 1162732, "vin": [ { "gen": { "height": 1162722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b17b59a1b544e8e904cc5b271696a72afe77a6d201a3326fc4e33a952f8fcfd" } } ], "extra": [ 1, 87, 71, 117, 253, 227, 168, 95, 129, 165, 4, 182, 103, 184, 97, 202, 139, 82, 195, 203, 207, 65, 84, 46, 167, 123, 176, 137, 214, 28, 220, 47, 177, 2, 17, 0, 0, 0, 2, 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