Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 805d4d327d51c2a87ecbdf1eb23b29460a67f2dbae531878436cf0eade645edd

Tx prefix hash: 965e0fb07f9305888cb51ec9224ebd27855bcbbfa2bc7a67014edfae06907c08
Tx public key: a5f7df1eb1c40d9c7447bf0b84ca6415d963a356e14cdc9130566acb2cd58541
Timestamp: 1729682035 Timestamp [UCT]: 2024-10-23 11:13:55 Age [y:d:h:m:s]: 00:218:06:44:03
Block: 1137795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155845 RingCT/type: yes/0
Extra: 01a5f7df1eb1c40d9c7447bf0b84ca6415d963a356e14cdc9130566acb2cd58541021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b05cdb94be4e4ca6eb4f3f729d2ddba8e84999e84e23ad6a12ee8451c247039 0.600000000000 1621354 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": 1137805, "vin": [ { "gen": { "height": 1137795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b05cdb94be4e4ca6eb4f3f729d2ddba8e84999e84e23ad6a12ee8451c247039" } } ], "extra": [ 1, 165, 247, 223, 30, 177, 196, 13, 156, 116, 71, 191, 11, 132, 202, 100, 21, 217, 99, 163, 86, 225, 76, 220, 145, 48, 86, 106, 203, 44, 213, 133, 65, 2, 17, 0, 0, 0, 3, 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