Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f01938371eb3f7d20dbf16e6920d0f012dfc01a7c67bbcee3b228b49ab5177f8

Tx prefix hash: 749154748598ccc5ce3efd3fb8f5dcf5d666e4773b31fdedba3e670f49512ada
Tx public key: 99618b6e68aee18b1f7b6a4e75390c4f26887fb101816d96c7205132fa8d5726
Timestamp: 1582062807 Timestamp [UCT]: 2020-02-18 21:53:27 Age [y:d:h:m:s]: 05:082:07:10:42
Block: 67748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1211906 RingCT/type: yes/0
Extra: 0199618b6e68aee18b1f7b6a4e75390c4f26887fb101816d96c7205132fa8d57260211000000034ac5aa02000000000000000000

1 output(s) for total of 366.035796594000 dcy

stealth address amount amount idx
00: 8178479652e63c4e2094915e569592079b70eaf5f5aa46931fb82d871f786c61 366.035796594000 124787 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": 67758, "vin": [ { "gen": { "height": 67748 } } ], "vout": [ { "amount": 366035796594, "target": { "key": "8178479652e63c4e2094915e569592079b70eaf5f5aa46931fb82d871f786c61" } } ], "extra": [ 1, 153, 97, 139, 110, 104, 174, 225, 139, 31, 123, 106, 78, 117, 57, 12, 79, 38, 136, 127, 177, 1, 129, 109, 150, 199, 32, 81, 50, 250, 141, 87, 38, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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