Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea445c1f7d07da8eced131b3e4b184e45d04964cf473259a9bcf23a7194131ae

Tx prefix hash: c7fe3579f8bc64c3f12bfae900dafd2d079121d7afcac287358fa425c293c325
Tx public key: ab36b6f8e349379a284ae71a8d7425cfe7a54761d50d3f838b10e53847f309b4
Timestamp: 1719336581 Timestamp [UCT]: 2024-06-25 17:29:41 Age [y:d:h:m:s]: 00:356:12:55:35
Block: 1052043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254722 RingCT/type: yes/0
Extra: 01ab36b6f8e349379a284ae71a8d7425cfe7a54761d50d3f838b10e53847f309b40211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aec701b9b69fcb06221711977d718554941376c9ecd9e734d19b0e6adfff83e1 0.600000000000 1522364 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": 1052053, "vin": [ { "gen": { "height": 1052043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aec701b9b69fcb06221711977d718554941376c9ecd9e734d19b0e6adfff83e1" } } ], "extra": [ 1, 171, 54, 182, 248, 227, 73, 55, 154, 40, 74, 231, 26, 141, 116, 37, 207, 231, 165, 71, 97, 213, 13, 63, 131, 139, 16, 229, 56, 71, 243, 9, 180, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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