Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a7b7c196079c06b1bca7d610a8246e9e2916812e294e9d214ab972361dedd75

Tx prefix hash: 398df3e616088006d2c808425bb6a9e3880bbba35cd0cca6583090c106b99d7d
Tx public key: 5bd54edaa5df79b1a6c888e5cea9277927cf2b67d6d4bcdd5ea25a8f6822c2ff
Timestamp: 1720319517 Timestamp [UCT]: 2024-07-07 02:31:57 Age [y:d:h:m:s]: 00:312:19:34:41
Block: 1060203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223531 RingCT/type: yes/0
Extra: 015bd54edaa5df79b1a6c888e5cea9277927cf2b67d6d4bcdd5ea25a8f6822c2ff02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95a26093b414aea182fe7253995ed23603eb9a44939128fdb95fe6288cc9f275 0.600000000000 1530674 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": 1060213, "vin": [ { "gen": { "height": 1060203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95a26093b414aea182fe7253995ed23603eb9a44939128fdb95fe6288cc9f275" } } ], "extra": [ 1, 91, 213, 78, 218, 165, 223, 121, 177, 166, 200, 136, 229, 206, 169, 39, 121, 39, 207, 43, 103, 214, 212, 188, 221, 94, 162, 90, 143, 104, 34, 194, 255, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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