Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f183ecb5f1f733d7de92f541d51f8f3587b6c8b9f538cd82809c429b68950f5c

Tx prefix hash: 41c0a29519c289c11aed890727c943970dfcf2836e464249b1cc832c7383c1b2
Tx public key: 0ac309140ba2be8d53e8fed538d3d20d3039be421bda4c2df6e7faff34728de6
Timestamp: 1698661521 Timestamp [UCT]: 2023-10-30 10:25:21 Age [y:d:h:m:s]: 01:158:10:48:01
Block: 880866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374231 RingCT/type: yes/0
Extra: 010ac309140ba2be8d53e8fed538d3d20d3039be421bda4c2df6e7faff34728de602110000000275e3f0e9000000000000000000

1 output(s) for total of 0.740159450000 dcy

stealth address amount amount idx
00: 458e55cb38ec5486d191a0162fea24c487b2698a94a6ec15fc7f12e68bcd3d95 0.740159450000 1336436 of 0

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": 880876, "vin": [ { "gen": { "height": 880866 } } ], "vout": [ { "amount": 740159450, "target": { "key": "458e55cb38ec5486d191a0162fea24c487b2698a94a6ec15fc7f12e68bcd3d95" } } ], "extra": [ 1, 10, 195, 9, 20, 11, 162, 190, 141, 83, 232, 254, 213, 56, 211, 210, 13, 48, 57, 190, 66, 27, 218, 76, 45, 246, 231, 250, 255, 52, 114, 141, 230, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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