Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86c2ec3b3301fc42ac3b88a60692d1ad4103ea7d185c707c90fa07f9f74be4e8

Tx prefix hash: b483ab0e72338a093dfc3aed48bc67f33d638be2bcc32a50faab5743442223ae
Tx public key: a1dc7cfaccae0143fe910e3066d7f443b163cc7c320d4708deafe87af20a08d6
Timestamp: 1723999436 Timestamp [UCT]: 2024-08-18 16:43:56 Age [y:d:h:m:s]: 00:306:10:21:01
Block: 1090718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218753 RingCT/type: yes/0
Extra: 01a1dc7cfaccae0143fe910e3066d7f443b163cc7c320d4708deafe87af20a08d602110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9be9539416b671191d3c38c937fc3b0a4c6d313f006e5cb91f2132217e265bd 0.600000000000 1565341 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": 1090728, "vin": [ { "gen": { "height": 1090718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9be9539416b671191d3c38c937fc3b0a4c6d313f006e5cb91f2132217e265bd" } } ], "extra": [ 1, 161, 220, 124, 250, 204, 174, 1, 67, 254, 145, 14, 48, 102, 215, 244, 67, 177, 99, 204, 124, 50, 13, 71, 8, 222, 175, 232, 122, 242, 10, 8, 214, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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