Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b678d41b3c7a83fbbbdcf61186d2393a4cc2dd07c93db45ad9cc63d2a4abebf9

Tx prefix hash: 612465d26f5633ab64ea79d0d42034f8eca3500b086441d4b597cb7f37219078
Tx public key: 002a8cf7d8ead5147f900869115b23a49d224a681e1557e6f72bd7a2f4aa9dd6
Timestamp: 1720979945 Timestamp [UCT]: 2024-07-14 17:59:05 Age [y:d:h:m:s]: 00:268:16:47:13
Block: 1065692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191963 RingCT/type: yes/0
Extra: 01002a8cf7d8ead5147f900869115b23a49d224a681e1557e6f72bd7a2f4aa9dd602110000001491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51b9d164f8c650717cc98fe83d68c81e5ecd2b71da00392fd62e1b16690350a3 0.600000000000 1536241 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": 1065702, "vin": [ { "gen": { "height": 1065692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51b9d164f8c650717cc98fe83d68c81e5ecd2b71da00392fd62e1b16690350a3" } } ], "extra": [ 1, 0, 42, 140, 247, 216, 234, 213, 20, 127, 144, 8, 105, 17, 91, 35, 164, 157, 34, 74, 104, 30, 21, 87, 230, 247, 43, 215, 162, 244, 170, 157, 214, 2, 17, 0, 0, 0, 20, 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