Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6772beb51fd75dc87db4f25ae38363cc93d805814ad2bb3df97a4c3e1a8b7a0b

Tx prefix hash: b4f6bbc0ac842530d5831c81206fe3def106047e1725efa5212d040bc13f568e
Tx public key: be4afbe4200ea24eba07c21e56bd057b83fe704a89cb85839682c4d21d3340a8
Timestamp: 1713914013 Timestamp [UCT]: 2024-04-23 23:13:33 Age [y:d:h:m:s]: 00:307:06:50:27
Block: 1007105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219632 RingCT/type: yes/0
Extra: 01be4afbe4200ea24eba07c21e56bd057b83fe704a89cb85839682c4d21d3340a80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bad70ccd31efba016cdb206b054fe3f7d5169ab4b1ffee007f21d14c11d6fac 0.600000000000 1468339 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": 1007115, "vin": [ { "gen": { "height": 1007105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bad70ccd31efba016cdb206b054fe3f7d5169ab4b1ffee007f21d14c11d6fac" } } ], "extra": [ 1, 190, 74, 251, 228, 32, 14, 162, 78, 186, 7, 194, 30, 86, 189, 5, 123, 131, 254, 112, 74, 137, 203, 133, 131, 150, 130, 196, 210, 29, 51, 64, 168, 2, 17, 0, 0, 0, 1, 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