Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42a0dfa98d3b44ff5f7a09a2167c09c632a8c8e93cbfbbe7fd33c40f692c671d

Tx prefix hash: d09854c5479802858505596ef39b0f7bc011550254ee0234f3fb106cc4d1ff02
Tx public key: 1e7768a14256b76e2f15749bc1fff5d62d72ceb7318021cd77e8cec1d0b1f5d9
Timestamp: 1735302430 Timestamp [UCT]: 2024-12-27 12:27:10 Age [y:d:h:m:s]: 00:355:06:44:47
Block: 1184282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251487 RingCT/type: yes/0
Extra: 011e7768a14256b76e2f15749bc1fff5d62d72ceb7318021cd77e8cec1d0b1f5d9021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b13156ca3a58247ce5dfe33c61a22c2d9128687c65305ad2841cb364d18ecb7 0.600000000000 1670739 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": 1184292, "vin": [ { "gen": { "height": 1184282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b13156ca3a58247ce5dfe33c61a22c2d9128687c65305ad2841cb364d18ecb7" } } ], "extra": [ 1, 30, 119, 104, 161, 66, 86, 183, 110, 47, 21, 116, 155, 193, 255, 245, 214, 45, 114, 206, 183, 49, 128, 33, 205, 119, 232, 206, 193, 208, 177, 245, 217, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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