Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9053cc18dde7b74dabddbb36598dca96c880dbc13964c56ea9a28b9bc5c7c1eb

Tx prefix hash: a4b5bace0ae3c472c2fd1fb17a69fefc2b4d6534c8da43433f8b22465385adf7
Tx public key: 9f437491957c40409b0f3f11faf5c24bc29d768a3cad55d9793f7421bb34c3e5
Timestamp: 1712160977 Timestamp [UCT]: 2024-04-03 16:16:17 Age [y:d:h:m:s]: 00:350:22:52:43
Block: 992546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250954 RingCT/type: yes/0
Extra: 019f437491957c40409b0f3f11faf5c24bc29d768a3cad55d9793f7421bb34c3e502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b48d3c6ffd26df1b6f227034f0474d70418ca495c6bbe7805f74bbb4eab99987 0.600000000000 1452894 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": 992556, "vin": [ { "gen": { "height": 992546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b48d3c6ffd26df1b6f227034f0474d70418ca495c6bbe7805f74bbb4eab99987" } } ], "extra": [ 1, 159, 67, 116, 145, 149, 124, 64, 64, 155, 15, 63, 17, 250, 245, 194, 75, 194, 157, 118, 138, 60, 173, 85, 217, 121, 63, 116, 33, 187, 52, 195, 229, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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