Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85ddd837376e9ae5ada01c24bbbd58572a0a41430baa8f9fb86e11cf09e6de8a

Tx prefix hash: cb6fda971c649d7c3712d224ef8d45e426da73aaeb974dc85f96f77d46a2e2b5
Tx public key: 17202943f37df26388b87ef466b2eac7f9bf5744d59f31e59d4360e3a309e197
Timestamp: 1720077915 Timestamp [UCT]: 2024-07-04 07:25:15 Age [y:d:h:m:s]: 00:255:19:37:57
Block: 1058200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182779 RingCT/type: yes/0
Extra: 0117202943f37df26388b87ef466b2eac7f9bf5744d59f31e59d4360e3a309e1970211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 660b56644fc748457ec5473630730662fe5e0f7d82bb01dfbd6bc130e37fa3e5 0.600000000000 1528649 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": 1058210, "vin": [ { "gen": { "height": 1058200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "660b56644fc748457ec5473630730662fe5e0f7d82bb01dfbd6bc130e37fa3e5" } } ], "extra": [ 1, 23, 32, 41, 67, 243, 125, 242, 99, 136, 184, 126, 244, 102, 178, 234, 199, 249, 191, 87, 68, 213, 159, 49, 229, 157, 67, 96, 227, 163, 9, 225, 151, 2, 17, 0, 0, 0, 4, 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