Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23fc2be5b2b6d947df5bd439fbbe7a7a717fe3f75e194efb6649cbe529df1afd

Tx prefix hash: 8255f6870b7a1ff5baf4f223188a794109bbad724e0763a4d170c7a13e1ca5cb
Tx public key: 706b3a29230ce80744f4292a71cb4a1e7be3b5e290340d94f4a4167be6210580
Timestamp: 1638974562 Timestamp [UCT]: 2021-12-08 14:42:42 Age [y:d:h:m:s]: 02:334:22:01:14
Block: 391128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 757403 RingCT/type: yes/0
Extra: 01706b3a29230ce80744f4292a71cb4a1e7be3b5e290340d94f4a4167be62105800211000000011cab2639000000000000000000

1 output(s) for total of 31.047807386000 dcy

stealth address amount amount idx
00: e63bffe8ef31bdebbbc4affef744787b18da5a7c7cbcaabefe59d54b90a2303d 31.047807386000 787333 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": 391138, "vin": [ { "gen": { "height": 391128 } } ], "vout": [ { "amount": 31047807386, "target": { "key": "e63bffe8ef31bdebbbc4affef744787b18da5a7c7cbcaabefe59d54b90a2303d" } } ], "extra": [ 1, 112, 107, 58, 41, 35, 12, 232, 7, 68, 244, 41, 42, 113, 203, 74, 30, 123, 227, 181, 226, 144, 52, 13, 148, 244, 164, 22, 123, 230, 33, 5, 128, 2, 17, 0, 0, 0, 1, 28, 171, 38, 57, 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