Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3c4e52d3eabc72780a86259e79a8243386a1f54ed995040e79fea138052fb7a

Tx prefix hash: 391f3d4d41e57e18fca7ddff8b3ca70fd871971a18f756d7a3ae265be87bbfcc
Tx public key: 3dcf42c11f4aaa9098964568afc3eb328a201cf6efb545a78f5b744b37d113b5
Timestamp: 1714301680 Timestamp [UCT]: 2024-04-28 10:54:40 Age [y:d:h:m:s]: 01:192:10:14:31
Block: 1010313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396153 RingCT/type: yes/0
Extra: 013dcf42c11f4aaa9098964568afc3eb328a201cf6efb545a78f5b744b37d113b50211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a6ac5e501a754c547fb7cad8c84f0a2d126fde8607aa6a66d367d4ca8ea68b0 0.600000000000 1472231 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": 1010323, "vin": [ { "gen": { "height": 1010313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a6ac5e501a754c547fb7cad8c84f0a2d126fde8607aa6a66d367d4ca8ea68b0" } } ], "extra": [ 1, 61, 207, 66, 193, 31, 74, 170, 144, 152, 150, 69, 104, 175, 195, 235, 50, 138, 32, 28, 246, 239, 181, 69, 167, 143, 91, 116, 75, 55, 209, 19, 181, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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