Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea51879fdc846436cd1a737b0f00301c5502a7315c9bcbdefa98a746d3cad905

Tx prefix hash: 8a3d2cd75a1b682af7c2ef1caeb81da963fb6c9cf5c463334c0a357d4a08c716
Tx public key: 236e7af31c3905d6d3171420f39ae4108da0dd0818a7fcbb9f8aa27d31bcbe05
Timestamp: 1732789779 Timestamp [UCT]: 2024-11-28 10:29:39 Age [y:d:h:m:s]: 00:117:04:51:29
Block: 1163492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83560 RingCT/type: yes/0
Extra: 01236e7af31c3905d6d3171420f39ae4108da0dd0818a7fcbb9f8aa27d31bcbe050211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3baca1d911743bfb2e09d6c8197b71ef04160a80e3eca6eac2d39afe606571e6 0.600000000000 1649159 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": 1163502, "vin": [ { "gen": { "height": 1163492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3baca1d911743bfb2e09d6c8197b71ef04160a80e3eca6eac2d39afe606571e6" } } ], "extra": [ 1, 35, 110, 122, 243, 28, 57, 5, 214, 211, 23, 20, 32, 243, 154, 228, 16, 141, 160, 221, 8, 24, 167, 252, 187, 159, 138, 162, 125, 49, 188, 190, 5, 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