Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4109cf27fb29e20f20dc1cbcb02026364056b59da2c7034900c0f4fae8a9261a

Tx prefix hash: 9e1c641d62e1f0732dcc5226151fca40f2c879a272d01da584015a4e9c6c65b5
Tx public key: 6319b7ea071e434fe66a7b06c5a0a5655277f3e3938b0ff8bc1a32bd5a9d1dc7
Timestamp: 1732568416 Timestamp [UCT]: 2024-11-25 21:00:16 Age [y:d:h:m:s]: 00:343:12:07:37
Block: 1161654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243035 RingCT/type: yes/0
Extra: 016319b7ea071e434fe66a7b06c5a0a5655277f3e3938b0ff8bc1a32bd5a9d1dc70211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc5ed788a139155006e5288c8b2d3cc4bfb9f813f4548a61582ae96ddbd89dea 0.600000000000 1647309 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": 1161664, "vin": [ { "gen": { "height": 1161654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc5ed788a139155006e5288c8b2d3cc4bfb9f813f4548a61582ae96ddbd89dea" } } ], "extra": [ 1, 99, 25, 183, 234, 7, 30, 67, 79, 230, 106, 123, 6, 197, 160, 165, 101, 82, 119, 243, 227, 147, 139, 15, 248, 188, 26, 50, 189, 90, 157, 29, 199, 2, 17, 0, 0, 0, 2, 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