Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e41098d7af0475b996d6b60d7b808af1f7b2260164b99a7a251051864bbd74bc

Tx prefix hash: 81f311d5d85365ceefd153e0f59328c7dc3dc0733a198e15e8ef6fe52d0f92f5
Tx public key: 01ea6b47a552572c22000445234b4b8cc7e843733119c37267389bb1bcae6a30
Timestamp: 1581949061 Timestamp [UCT]: 2020-02-17 14:17:41 Age [y:d:h:m:s]: 05:262:07:40:43
Block: 66832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1338229 RingCT/type: yes/0
Extra: 0101ea6b47a552572c22000445234b4b8cc7e843733119c37267389bb1bcae6a3002110000000256c366d3000000000000000000

1 output(s) for total of 368.602816238000 dcy

stealth address amount amount idx
00: 577f391516078092b0720c61b3da66ed7c6170aed68e37be0a5d8a13043708fa 368.602816238000 123046 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": 66842, "vin": [ { "gen": { "height": 66832 } } ], "vout": [ { "amount": 368602816238, "target": { "key": "577f391516078092b0720c61b3da66ed7c6170aed68e37be0a5d8a13043708fa" } } ], "extra": [ 1, 1, 234, 107, 71, 165, 82, 87, 44, 34, 0, 4, 69, 35, 75, 75, 140, 199, 232, 67, 115, 49, 25, 195, 114, 103, 56, 155, 177, 188, 174, 106, 48, 2, 17, 0, 0, 0, 2, 86, 195, 102, 211, 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