Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e68c9f2f53b6302b76e6a1b60f696391ef39418d634c2abdd02ed00b17c0a795

Tx prefix hash: 85b1f5be60cf8a8a2e54a8e33f15150358a2e146c983a71bae25d822d00622e1
Tx public key: 6b1bef601cb8e3d2ac980b4571feaa8d01be77cfc3be5127a2a2920de6eb7ce5
Timestamp: 1698516487 Timestamp [UCT]: 2023-10-28 18:08:07 Age [y:d:h:m:s]: 02:012:01:42:34
Block: 879661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528203 RingCT/type: yes/0
Extra: 016b1bef601cb8e3d2ac980b4571feaa8d01be77cfc3be5127a2a2920de6eb7ce502110000000136a45730000000000000000000

1 output(s) for total of 0.746995448000 dcy

stealth address amount amount idx
00: 0fd3aeaf8144b36d8b72ba9d1b4ce21cbc7db9d1d58c602e506b19de0a8f65cd 0.746995448000 1335195 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": 879671, "vin": [ { "gen": { "height": 879661 } } ], "vout": [ { "amount": 746995448, "target": { "key": "0fd3aeaf8144b36d8b72ba9d1b4ce21cbc7db9d1d58c602e506b19de0a8f65cd" } } ], "extra": [ 1, 107, 27, 239, 96, 28, 184, 227, 210, 172, 152, 11, 69, 113, 254, 170, 141, 1, 190, 119, 207, 195, 190, 81, 39, 162, 162, 146, 13, 230, 235, 124, 229, 2, 17, 0, 0, 0, 1, 54, 164, 87, 48, 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