Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 362d8e167218bd8cd1ad9d40c2f2f08aab85489e150305e16ac5772575298d00

Tx prefix hash: 837ff79750cf3fbc70b8c82a5aee8c077b53718f82685c5bfcbab5716d5810e7
Tx public key: 316b1ce719b3cca7c69d65ebdb62752303e9c93766d4e3b7cd74dc4e2ce14ebc
Timestamp: 1700783546 Timestamp [UCT]: 2023-11-23 23:52:26 Age [y:d:h:m:s]: 01:097:15:55:27
Block: 898231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330950 RingCT/type: yes/0
Extra: 01316b1ce719b3cca7c69d65ebdb62752303e9c93766d4e3b7cd74dc4e2ce14ebc02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.648317597000 dcy

stealth address amount amount idx
00: 6c2cda9d709aaf90d293e082a23a701fbe0264ba653c49a1af2973737a8cd46f 0.648317597000 1354642 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": 898241, "vin": [ { "gen": { "height": 898231 } } ], "vout": [ { "amount": 648317597, "target": { "key": "6c2cda9d709aaf90d293e082a23a701fbe0264ba653c49a1af2973737a8cd46f" } } ], "extra": [ 1, 49, 107, 28, 231, 25, 179, 204, 167, 198, 157, 101, 235, 219, 98, 117, 35, 3, 233, 201, 55, 102, 212, 227, 183, 205, 116, 220, 78, 44, 225, 78, 188, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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