Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f7a88f5bd567aea06da1cf06cc6173a8a7e4987d809830918629128be5bb9b4

Tx prefix hash: a41fb957b6a2b3d0b0c1f26366c9b737f2569fc296f8eb9cfe3fa9bf7df62100
Tx public key: 98c7541d79a0dd6668c204e3363d50c0ec08d796222905aed4974621e82c598f
Timestamp: 1638608155 Timestamp [UCT]: 2021-12-04 08:55:55 Age [y:d:h:m:s]: 02:337:05:50:55
Block: 388133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 759015 RingCT/type: yes/0
Extra: 0198c7541d79a0dd6668c204e3363d50c0ec08d796222905aed4974621e82c598f02110000002bf6cc1430000000000000000000

1 output(s) for total of 31.765421186000 dcy

stealth address amount amount idx
00: 2af956e22c7d8db795e919c151807ee259e47be399e9344268778f0e3ec0e52b 31.765421186000 782616 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": 388143, "vin": [ { "gen": { "height": 388133 } } ], "vout": [ { "amount": 31765421186, "target": { "key": "2af956e22c7d8db795e919c151807ee259e47be399e9344268778f0e3ec0e52b" } } ], "extra": [ 1, 152, 199, 84, 29, 121, 160, 221, 102, 104, 194, 4, 227, 54, 61, 80, 192, 236, 8, 215, 150, 34, 41, 5, 174, 212, 151, 70, 33, 232, 44, 89, 143, 2, 17, 0, 0, 0, 43, 246, 204, 20, 48, 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