Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e38c4c7192799ed011fa5be2fe84a5132e02d6ce79c039a08af992dadc158b2

Tx prefix hash: d560e5c4554ccb6f3e8bd9e78d1842512b2c6063c0d595885f937b6c8a42547d
Tx public key: ad2f9574f14ff822430c9f17bfd33d827d32636612eef0294be97556aa64e6cd
Timestamp: 1714144779 Timestamp [UCT]: 2024-04-26 15:19:39 Age [y:d:h:m:s]: 00:202:19:22:20
Block: 1009012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145183 RingCT/type: yes/0
Extra: 01ad2f9574f14ff822430c9f17bfd33d827d32636612eef0294be97556aa64e6cd02110000000d0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c53df980d080e16f550c110d6e8dc2177fb9eb71dff7d089bcf1ac488fd19c5 0.600000000000 1470552 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": 1009022, "vin": [ { "gen": { "height": 1009012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c53df980d080e16f550c110d6e8dc2177fb9eb71dff7d089bcf1ac488fd19c5" } } ], "extra": [ 1, 173, 47, 149, 116, 241, 79, 248, 34, 67, 12, 159, 23, 191, 211, 61, 130, 125, 50, 99, 102, 18, 238, 240, 41, 75, 233, 117, 86, 170, 100, 230, 205, 2, 17, 0, 0, 0, 13, 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