Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6eb630cfab270b5dac13d176f193cd5ed616ab0caf50f51c616616a8fbc5312d

Tx prefix hash: 7401639c69caec1da3e8549b2dd333f59785abce3b32d6276d90c303bb91c8e2
Tx public key: 85e84868ccf9f249091fbd4f0ba67538072a12f8ede0d0c1866b4b83102e083a
Timestamp: 1699804649 Timestamp [UCT]: 2023-11-12 15:57:29 Age [y:d:h:m:s]: 01:150:20:11:36
Block: 890134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368997 RingCT/type: yes/0
Extra: 0185e84868ccf9f249091fbd4f0ba67538072a12f8ede0d0c1866b4b83102e083a0211000000054b8f5122000000000000000000

1 output(s) for total of 0.689630632000 dcy

stealth address amount amount idx
00: 59ff25dd53551b5d45f8c9111c9dea0eabe5185f27f54fb978c649a205afbe50 0.689630632000 1346153 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": 890144, "vin": [ { "gen": { "height": 890134 } } ], "vout": [ { "amount": 689630632, "target": { "key": "59ff25dd53551b5d45f8c9111c9dea0eabe5185f27f54fb978c649a205afbe50" } } ], "extra": [ 1, 133, 232, 72, 104, 204, 249, 242, 73, 9, 31, 189, 79, 11, 166, 117, 56, 7, 42, 18, 248, 237, 224, 208, 193, 134, 107, 75, 131, 16, 46, 8, 58, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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