Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fae4b28c5bb7f059d9a51011d64f03393f689bf64ac45aaf1f4a7cd53601b07c

Tx prefix hash: 588643c952c5c9e77c920ec1937d5217e4ef8ee7f62aefbd2761ddaffc98b418
Tx public key: ee01f1aa17eb489b015735baa7dbe9d8fcf85a13bd94f7bc6cdd39aec925d332
Timestamp: 1712668402 Timestamp [UCT]: 2024-04-09 13:13:22 Age [y:d:h:m:s]: 01:256:17:21:59
Block: 996749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442215 RingCT/type: yes/0
Extra: 01ee01f1aa17eb489b015735baa7dbe9d8fcf85a13bd94f7bc6cdd39aec925d33202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc6da0e9bf22da99f2ea47d18ca4e4f70926e483eb2ec8dcd10c343137622e81 0.600000000000 1457175 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": 996759, "vin": [ { "gen": { "height": 996749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc6da0e9bf22da99f2ea47d18ca4e4f70926e483eb2ec8dcd10c343137622e81" } } ], "extra": [ 1, 238, 1, 241, 170, 23, 235, 72, 155, 1, 87, 53, 186, 167, 219, 233, 216, 252, 248, 90, 19, 189, 148, 247, 188, 108, 221, 57, 174, 201, 37, 211, 50, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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