Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 909e8a9e52f8459fd3efa1967414913fa6f2a03ddb4a10c9dc1a6b3e5847d1d9

Tx prefix hash: 6ec9d0512ca969bd2eceabaebf40fcfe12994bf100a8b2bc1871923f5c4cd231
Tx public key: 17768344dda77053f4d0a5e78a03e5f23efcac299db15aa9804bc76c701c5bde
Timestamp: 1708194408 Timestamp [UCT]: 2024-02-17 18:26:48 Age [y:d:h:m:s]: 01:035:00:21:44
Block: 959678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286052 RingCT/type: yes/0
Extra: 0117768344dda77053f4d0a5e78a03e5f23efcac299db15aa9804bc76c701c5bde02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe38dc3c94f3f75e7deb627524d2c89058a847e882774b7df02ac93fef6b7d9f 0.600000000000 1419231 of 15

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": 959688, "vin": [ { "gen": { "height": 959678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe38dc3c94f3f75e7deb627524d2c89058a847e882774b7df02ac93fef6b7d9f" } } ], "extra": [ 1, 23, 118, 131, 68, 221, 167, 112, 83, 244, 208, 165, 231, 138, 3, 229, 242, 62, 252, 172, 41, 157, 177, 90, 169, 128, 75, 199, 108, 112, 28, 91, 222, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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