Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4e97d2cf736f66cf0d965f56d1518ae068604fba4e77ff1dd4f6a872992bb10

Tx prefix hash: 5486deb44633a240078641c4526aaa150a82699f2f2c19d3992f0d2285eb082e
Tx public key: 0bef1509c4dc24bc47ae457b271e9fe445ef30ca92084a9e0a5da752899ff3dd
Timestamp: 1718515623 Timestamp [UCT]: 2024-06-16 05:27:03 Age [y:d:h:m:s]: 00:278:19:10:03
Block: 1045266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199206 RingCT/type: yes/0
Extra: 010bef1509c4dc24bc47ae457b271e9fe445ef30ca92084a9e0a5da752899ff3dd02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a18f0308c9e5e00fa65196b64927d096e7cd2b4ae431888978d899e21396684 0.600000000000 1514791 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": 1045276, "vin": [ { "gen": { "height": 1045266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a18f0308c9e5e00fa65196b64927d096e7cd2b4ae431888978d899e21396684" } } ], "extra": [ 1, 11, 239, 21, 9, 196, 220, 36, 188, 71, 174, 69, 123, 39, 30, 159, 228, 69, 239, 48, 202, 146, 8, 74, 158, 10, 93, 167, 82, 137, 159, 243, 221, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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