Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 029a8f310aba4c558bec5790e0702859dc05e87b044f49f63ee981074a0ac017

Tx prefix hash: 3c040de18dcc8a9a6599f8ea0b77af48f9e93db1a8cf9d452d12f6bfd2472a32
Tx public key: 60a9c7233f3dcd3cbd1378f276829066a9ac262d1a05b3eaa5bcd0a26035818c
Timestamp: 1732734560 Timestamp [UCT]: 2024-11-27 19:09:20 Age [y:d:h:m:s]: 00:117:02:49:53
Block: 1163030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83501 RingCT/type: yes/0
Extra: 0160a9c7233f3dcd3cbd1378f276829066a9ac262d1a05b3eaa5bcd0a26035818c0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce905ad83466009d43a594b59889e4d70a34dca1dcf259bef839303375397c28 0.600000000000 1648693 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": 1163040, "vin": [ { "gen": { "height": 1163030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce905ad83466009d43a594b59889e4d70a34dca1dcf259bef839303375397c28" } } ], "extra": [ 1, 96, 169, 199, 35, 63, 61, 205, 60, 189, 19, 120, 242, 118, 130, 144, 102, 169, 172, 38, 45, 26, 5, 179, 234, 165, 188, 208, 162, 96, 53, 129, 140, 2, 17, 0, 0, 0, 6, 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