Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f381e87ecd4ddba600931ef6464da42c7b77cce3c1e239b463b4ef12ef04df9b

Tx prefix hash: c9aaffdfcec198f3f3bfa40db9b3dd3d8b6a3f2a6bfc3910d0348427e0c51a59
Tx public key: 172586836127b10a04e52ea1e840a7ca39876dc44e46de2c74e92cb3799b9d09
Timestamp: 1708719990 Timestamp [UCT]: 2024-02-23 20:26:30 Age [y:d:h:m:s]: 01:043:21:15:24
Block: 964041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292372 RingCT/type: yes/0
Extra: 01172586836127b10a04e52ea1e840a7ca39876dc44e46de2c74e92cb3799b9d0902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddea1654eaadc1925b806d1c4f5e700956fdb0981760358324b774c1bda03838 0.600000000000 1423768 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": 964051, "vin": [ { "gen": { "height": 964041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddea1654eaadc1925b806d1c4f5e700956fdb0981760358324b774c1bda03838" } } ], "extra": [ 1, 23, 37, 134, 131, 97, 39, 177, 10, 4, 229, 46, 161, 232, 64, 167, 202, 57, 135, 109, 196, 78, 70, 222, 44, 116, 233, 44, 179, 121, 155, 157, 9, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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