Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 995a698b1f0cfb25cf985ea09fed957169fd28411334fd0196d8ae998ee95e6f

Tx prefix hash: a85146b437ae14d8d64f2809597786f51c96b65f12b14b662b22b0f3729cceb1
Tx public key: f0ae2059fbec0f20329eff5cef16da114664a6353e611d975e2a452a7b8304f7
Timestamp: 1694238745 Timestamp [UCT]: 2023-09-09 05:52:25 Age [y:d:h:m:s]: 01:222:04:21:54
Block: 844161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419913 RingCT/type: yes/0
Extra: 01f0ae2059fbec0f20329eff5cef16da114664a6353e611d975e2a452a7b8304f70211000000064b8f5122000000000000000000

1 output(s) for total of 0.979364244000 dcy

stealth address amount amount idx
00: f0690169f98d8c1464e7046c1106d0a00fcb00d832e81efe9ca55d1a3af77075 0.979364244000 1297453 of 0

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": 844171, "vin": [ { "gen": { "height": 844161 } } ], "vout": [ { "amount": 979364244, "target": { "key": "f0690169f98d8c1464e7046c1106d0a00fcb00d832e81efe9ca55d1a3af77075" } } ], "extra": [ 1, 240, 174, 32, 89, 251, 236, 15, 32, 50, 158, 255, 92, 239, 22, 218, 17, 70, 100, 166, 53, 62, 97, 29, 151, 94, 42, 69, 42, 123, 131, 4, 247, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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