Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c01bfe50d752a0dc214a8630adc7063abf2eb258f9367fdf1453e8327b279e1e

Tx prefix hash: 589464435490e9a42eaf6dcd6a525e12395f6a3c869af97e74a51cd9ff216623
Tx public key: ec40d16aa1c0505ec6e3835066e0015806c37e6bdc89c05d8ed74aa0a3f625b8
Timestamp: 1710428046 Timestamp [UCT]: 2024-03-14 14:54:06 Age [y:d:h:m:s]: 01:063:19:50:25
Block: 978221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306614 RingCT/type: yes/0
Extra: 01ec40d16aa1c0505ec6e3835066e0015806c37e6bdc89c05d8ed74aa0a3f625b80211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e801d9dba496bdbc05c4cd37331f24ef0feeb3d4698641f66bbc4d10abe4edc4 0.600000000000 1438242 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": 978231, "vin": [ { "gen": { "height": 978221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e801d9dba496bdbc05c4cd37331f24ef0feeb3d4698641f66bbc4d10abe4edc4" } } ], "extra": [ 1, 236, 64, 209, 106, 161, 192, 80, 94, 198, 227, 131, 80, 102, 224, 1, 88, 6, 195, 126, 107, 220, 137, 192, 93, 142, 215, 74, 160, 163, 246, 37, 184, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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