Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a46c65032daef976f8e1ce8d64d03de2309d8ad81bcd5ffa97631b6fda567938

Tx prefix hash: 8eb6924bb63e154dbaf90fe31be52287fa1040e93d353e2c7efbce34a28a631b
Tx public key: 363354d3c127f141be253d5f2ebe83ae0c6acc7650c6b6edf9a9c215ffde1b2d
Timestamp: 1714929985 Timestamp [UCT]: 2024-05-05 17:26:25 Age [y:d:h:m:s]: 00:248:11:53:36
Block: 1015528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177855 RingCT/type: yes/0
Extra: 01363354d3c127f141be253d5f2ebe83ae0c6acc7650c6b6edf9a9c215ffde1b2d0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32801ac3680a6585c9d7d3f11986f59ca8dacdd71339523177585f7091c97da6 0.600000000000 1478923 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": 1015538, "vin": [ { "gen": { "height": 1015528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32801ac3680a6585c9d7d3f11986f59ca8dacdd71339523177585f7091c97da6" } } ], "extra": [ 1, 54, 51, 84, 211, 193, 39, 241, 65, 190, 37, 61, 95, 46, 190, 131, 174, 12, 106, 204, 118, 80, 198, 182, 237, 249, 169, 194, 21, 255, 222, 27, 45, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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