Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e825e67b0f77b5426e9fd30bfc7473161b1e769b04b9dc07b5467c96fae0f2f4

Tx prefix hash: 7745ec251d3162ff6725126538764d58a42cdcddd184fc6e6a89b66dfdb7ca34
Tx public key: 785c639a012277321ec4e2bd27a3e17cddd9109ca777bbf76343a68174ea02f5
Timestamp: 1674181310 Timestamp [UCT]: 2023-01-20 02:21:50 Age [y:d:h:m:s]: 02:094:18:41:30
Block: 678561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 589411 RingCT/type: yes/0
Extra: 01785c639a012277321ec4e2bd27a3e17cddd9109ca777bbf76343a68174ea02f50211000000015029cbac000000000000000000

1 output(s) for total of 3.464540700000 dcy

stealth address amount amount idx
00: e6b2ff6a4aea89355c1af48c4aeece9a343d08f11b373cdd844e796a1ef7964f 3.464540700000 1120448 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": 678571, "vin": [ { "gen": { "height": 678561 } } ], "vout": [ { "amount": 3464540700, "target": { "key": "e6b2ff6a4aea89355c1af48c4aeece9a343d08f11b373cdd844e796a1ef7964f" } } ], "extra": [ 1, 120, 92, 99, 154, 1, 34, 119, 50, 30, 196, 226, 189, 39, 163, 225, 124, 221, 217, 16, 156, 167, 119, 187, 247, 99, 67, 166, 129, 116, 234, 2, 245, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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