Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f48521bd0c312d3fbb42f1ba8c168d0850bc5ac5f9f81a915e0a9c9bd98f1759

Tx prefix hash: 8a346182ecf4ab6143ebcc3c07ab24903f1ca62c51e881f0e86ddf8bd4a8ff26
Tx public key: 42ada7781c30be8434b0e714ea99604486a07ea22d47bdb7ab697127c9e58ef3
Timestamp: 1713483386 Timestamp [UCT]: 2024-04-18 23:36:26 Age [y:d:h:m:s]: 00:155:20:14:51
Block: 1003522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111637 RingCT/type: yes/0
Extra: 0142ada7781c30be8434b0e714ea99604486a07ea22d47bdb7ab697127c9e58ef302110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06a2a6755e0a7a46da5891f25d72e10ef2fb6cfdb529c7a1465ead1c94cdadc2 0.600000000000 1464064 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": 1003532, "vin": [ { "gen": { "height": 1003522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06a2a6755e0a7a46da5891f25d72e10ef2fb6cfdb529c7a1465ead1c94cdadc2" } } ], "extra": [ 1, 66, 173, 167, 120, 28, 48, 190, 132, 52, 176, 231, 20, 234, 153, 96, 68, 134, 160, 126, 162, 45, 71, 189, 183, 171, 105, 113, 39, 201, 229, 142, 243, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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