Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 340296ad7f95c340c8525ad56b6b2e88052a8eeb2d367df08bbd617df9e6dae2

Tx prefix hash: 4ea963761491f07028d73a41af5ee19d717b965a8bfd0295b48b1da7b711ba66
Tx public key: e6cdea90bdcebd20420199e50b826409c31be2c619d7ddfa26a6d27d7ade9f35
Timestamp: 1723646849 Timestamp [UCT]: 2024-08-14 14:47:29 Age [y:d:h:m:s]: 00:244:22:21:27
Block: 1087798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174928 RingCT/type: yes/0
Extra: 01e6cdea90bdcebd20420199e50b826409c31be2c619d7ddfa26a6d27d7ade9f3502110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1584f5e4ac38587a748e938c910e00af35bf71e2d5e08e46b3607711e9abb54 0.600000000000 1562409 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": 1087808, "vin": [ { "gen": { "height": 1087798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1584f5e4ac38587a748e938c910e00af35bf71e2d5e08e46b3607711e9abb54" } } ], "extra": [ 1, 230, 205, 234, 144, 189, 206, 189, 32, 66, 1, 153, 229, 11, 130, 100, 9, 195, 27, 226, 198, 25, 215, 221, 250, 38, 166, 210, 125, 122, 222, 159, 53, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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