Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae98e06eaf543be66007d24e3b660a0131a0a26d018b24634679c485638419f4

Tx prefix hash: 6819d95aced860fec551a4c619de98d0bd83b064c4e488950fa430efff12ac89
Tx public key: 7523acf6e83be9f0a4e34a70d19d6707b391be17361a60e920c67c497b64e0fa
Timestamp: 1699750243 Timestamp [UCT]: 2023-11-12 00:50:43 Age [y:d:h:m:s]: 01:105:09:22:40
Block: 889678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336473 RingCT/type: yes/0
Extra: 017523acf6e83be9f0a4e34a70d19d6707b391be17361a60e920c67c497b64e0fa021100000001faf35c9c000000000000000000

1 output(s) for total of 0.692034047000 dcy

stealth address amount amount idx
00: 490286f0795c3ae69c7640affa17a8b0faf9b10ef5abb1907cec80dda5de3838 0.692034047000 1345687 of 0

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": 889688, "vin": [ { "gen": { "height": 889678 } } ], "vout": [ { "amount": 692034047, "target": { "key": "490286f0795c3ae69c7640affa17a8b0faf9b10ef5abb1907cec80dda5de3838" } } ], "extra": [ 1, 117, 35, 172, 246, 232, 59, 233, 240, 164, 227, 74, 112, 209, 157, 103, 7, 179, 145, 190, 23, 54, 26, 96, 233, 32, 198, 124, 73, 123, 100, 224, 250, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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