Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a5b61c92eb66250e41017ea5e2b6fc48ea5a04ae17622e0ee8688f5abf4e931

Tx prefix hash: cf73c126d30f3f72ef38d3b2221971056d530fa06b8a90a997d2403cdc5e6fde
Tx public key: 809416ab641636ffee9e8f4116211ac6262e1cf897c1d361c4bcdc075b5e7a48
Timestamp: 1733278918 Timestamp [UCT]: 2024-12-04 02:21:58 Age [y:d:h:m:s]: 00:116:07:03:00
Block: 1167537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82920 RingCT/type: yes/0
Extra: 01809416ab641636ffee9e8f4116211ac6262e1cf897c1d361c4bcdc075b5e7a480211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0f7b4f0b7a9425766d5752e5a4b57c1bf993deb0240b25b0d3e32ce1783d53f 0.600000000000 1653234 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": 1167547, "vin": [ { "gen": { "height": 1167537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0f7b4f0b7a9425766d5752e5a4b57c1bf993deb0240b25b0d3e32ce1783d53f" } } ], "extra": [ 1, 128, 148, 22, 171, 100, 22, 54, 255, 238, 158, 143, 65, 22, 33, 26, 198, 38, 46, 28, 248, 151, 193, 211, 97, 196, 188, 220, 7, 91, 94, 122, 72, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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