Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ae8b8c8a67ba155b3586a75cdf6fda5d948a67fb4401c6c415b037cab79cdf6

Tx prefix hash: 1b31b20fc1493147551d2796a2b3f89a53e7b0441f287e0400321bf734dd6887
Tx public key: 11c01dcbed8cb0e8bdca928a3f2db02f07a83ea8c6a301cdb9a5c72893424d05
Timestamp: 1715859021 Timestamp [UCT]: 2024-05-16 11:30:21 Age [y:d:h:m:s]: 00:283:11:43:09
Block: 1023226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202594 RingCT/type: yes/0
Extra: 0111c01dcbed8cb0e8bdca928a3f2db02f07a83ea8c6a301cdb9a5c72893424d0502110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b08b80f1a9a7970ddd5d83d1cb2ea1109fa60b143a8bb2ed8c1352867f37942 0.600000000000 1488067 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": 1023236, "vin": [ { "gen": { "height": 1023226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b08b80f1a9a7970ddd5d83d1cb2ea1109fa60b143a8bb2ed8c1352867f37942" } } ], "extra": [ 1, 17, 192, 29, 203, 237, 140, 176, 232, 189, 202, 146, 138, 63, 45, 176, 47, 7, 168, 62, 168, 198, 163, 1, 205, 185, 165, 199, 40, 147, 66, 77, 5, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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