Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62ecac5f5057a817a22235db7eb1b49b1dd96bf6d9b707cb39b21e10f1da4e52

Tx prefix hash: bad51eac24a39dd233b281182cb664d083067a5f1e989087c8eb9b2abf0fc25f
Tx public key: 1024a181bf4c785c8214f4dc520840aa2113d5226051aa0fb0d69ab9424a11ee
Timestamp: 1726468529 Timestamp [UCT]: 2024-09-16 06:35:29 Age [y:d:h:m:s]: 00:274:09:19:09
Block: 1111177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195873 RingCT/type: yes/0
Extra: 011024a181bf4c785c8214f4dc520840aa2113d5226051aa0fb0d69ab9424a11ee021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6022ccd81bd42199c5ef6376a9a0cba476f422f9bbf59d2b21c519166e57b255 0.600000000000 1590048 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": 1111187, "vin": [ { "gen": { "height": 1111177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6022ccd81bd42199c5ef6376a9a0cba476f422f9bbf59d2b21c519166e57b255" } } ], "extra": [ 1, 16, 36, 161, 129, 191, 76, 120, 92, 130, 20, 244, 220, 82, 8, 64, 170, 33, 19, 213, 34, 96, 81, 170, 15, 176, 214, 154, 185, 66, 74, 17, 238, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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