Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78410ab606f14e924514e68df41a0e240b8bddebd27175b0eb0896023ee6d0a3

Tx prefix hash: 2e40539068f2917453c682e81090e9a42e5d4a22ee001771d36b0cba9eb929c3
Tx public key: 658b0991e3964c840625cac0777f1ead85f6d5ccf7cc9aa4ee1f9ced1efbc31f
Timestamp: 1718316699 Timestamp [UCT]: 2024-06-13 22:11:39 Age [y:d:h:m:s]: 00:299:15:38:29
Block: 1043605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214138 RingCT/type: yes/0
Extra: 01658b0991e3964c840625cac0777f1ead85f6d5ccf7cc9aa4ee1f9ced1efbc31f0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13e897d3b5ec798962af38edbcad93cec2c8adaf71bea287cfbe0b5534970b3f 0.600000000000 1512762 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": 1043615, "vin": [ { "gen": { "height": 1043605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13e897d3b5ec798962af38edbcad93cec2c8adaf71bea287cfbe0b5534970b3f" } } ], "extra": [ 1, 101, 139, 9, 145, 227, 150, 76, 132, 6, 37, 202, 192, 119, 127, 30, 173, 133, 246, 213, 204, 247, 204, 154, 164, 238, 31, 156, 237, 30, 251, 195, 31, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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