Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6126e9c2e1be12c4d2e1138f4f92a398014c15085bec0a921f048980f67b92d

Tx prefix hash: 4d422a65f038a8529de1f63408bf6ff93dea287df46f63a3c798ebe70681c58c
Tx public key: 3c92e672d66c4034594ccc7014c88c471585d9aa546eae5a5a9423717b37621f
Timestamp: 1696092175 Timestamp [UCT]: 2023-09-30 16:42:55 Age [y:d:h:m:s]: 01:192:19:39:21
Block: 859547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398868 RingCT/type: yes/0
Extra: 013c92e672d66c4034594ccc7014c88c471585d9aa546eae5a5a9423717b37621f021100000001faf35c9c000000000000000000

1 output(s) for total of 0.870891430000 dcy

stealth address amount amount idx
00: 28e978d571704e0d2bc887c4522fb5f993407f3a925e762c37248adb302a3e97 0.870891430000 1313779 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": 859557, "vin": [ { "gen": { "height": 859547 } } ], "vout": [ { "amount": 870891430, "target": { "key": "28e978d571704e0d2bc887c4522fb5f993407f3a925e762c37248adb302a3e97" } } ], "extra": [ 1, 60, 146, 230, 114, 214, 108, 64, 52, 89, 76, 204, 112, 20, 200, 140, 71, 21, 133, 217, 170, 84, 110, 174, 90, 90, 148, 35, 113, 123, 55, 98, 31, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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