Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b1662666e7aa53edf12baaa906759f3f99c56c576e0625ec8b6462301a38ed0

Tx prefix hash: e44dd04a2b6d31a3bb79c7b7faac10e2b73fbc4bec802bd2f0af7a9bb491f2ce
Tx public key: 17a4da91efe3dbd2acbab40cf0a37b21effc8609e5c4d33cf3c6db0234a5ebe3
Timestamp: 1650625657 Timestamp [UCT]: 2022-04-22 11:07:37 Age [y:d:h:m:s]: 03:193:06:24:30
Block: 485622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 916460 RingCT/type: yes/0
Extra: 0117a4da91efe3dbd2acbab40cf0a37b21effc8609e5c4d33cf3c6db0234a5ebe302110000000ac9067537000000000000000000

1 output(s) for total of 15.098900310000 dcy

stealth address amount amount idx
00: 06f66b3311a8045fc9716aaafdf39707ed944f620844dd925c160cfc02bf3ebc 15.098900310000 907737 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": 485632, "vin": [ { "gen": { "height": 485622 } } ], "vout": [ { "amount": 15098900310, "target": { "key": "06f66b3311a8045fc9716aaafdf39707ed944f620844dd925c160cfc02bf3ebc" } } ], "extra": [ 1, 23, 164, 218, 145, 239, 227, 219, 210, 172, 186, 180, 12, 240, 163, 123, 33, 239, 252, 134, 9, 229, 196, 211, 60, 243, 198, 219, 2, 52, 165, 235, 227, 2, 17, 0, 0, 0, 10, 201, 6, 117, 55, 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