Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d16619240dce0c4281a208bc051622f76944dfbfa947ff3c20edb2f635cec4

Tx prefix hash: 73a58fe8e8224ffd8746283049ccf2a1a1182f88c44bb9e7a50f501cc86c8e6b
Tx public key: 9be811ec94c4a78dd25f04b15c5407542023adc43343f58fa5a3fa4b4ff88bf3
Timestamp: 1703002245 Timestamp [UCT]: 2023-12-19 16:10:45 Age [y:d:h:m:s]: 01:111:19:35:16
Block: 916644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341041 RingCT/type: yes/0
Extra: 019be811ec94c4a78dd25f04b15c5407542023adc43343f58fa5a3fa4b4ff88bf3021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31cc062773625e314638ae61aeb9650d3360a3f9ff3d81df3e9989f8e791bcf2 0.600000000000 1374202 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": 916654, "vin": [ { "gen": { "height": 916644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31cc062773625e314638ae61aeb9650d3360a3f9ff3d81df3e9989f8e791bcf2" } } ], "extra": [ 1, 155, 232, 17, 236, 148, 196, 167, 141, 210, 95, 4, 177, 92, 84, 7, 84, 32, 35, 173, 196, 51, 67, 245, 143, 165, 163, 250, 75, 79, 248, 139, 243, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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