Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6336e0ef98278a0930c56b657f27434e81feb2af70df8d96042be29f96fa4ba3

Tx prefix hash: 731dc9d07d9888bf34a5ee6e578e46a0dc0d5915e53998d8528f9a1d1ac39b63
Tx public key: 806062ecd62b6fddea6b3b1b12243d35d0807ead11448b2945e8f61e3e7e2afd
Timestamp: 1700317204 Timestamp [UCT]: 2023-11-18 14:20:04 Age [y:d:h:m:s]: 01:058:14:42:40
Block: 894379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303276 RingCT/type: yes/0
Extra: 01806062ecd62b6fddea6b3b1b12243d35d0807ead11448b2945e8f61e3e7e2afd0211000000024b8f5122000000000000000000

1 output(s) for total of 0.667653439000 dcy

stealth address amount amount idx
00: 891342b6fcc5c58a7d5f106d7d7f4eb04c3de38726426f6d43a2f6ae4b450dde 0.667653439000 1350578 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": 894389, "vin": [ { "gen": { "height": 894379 } } ], "vout": [ { "amount": 667653439, "target": { "key": "891342b6fcc5c58a7d5f106d7d7f4eb04c3de38726426f6d43a2f6ae4b450dde" } } ], "extra": [ 1, 128, 96, 98, 236, 214, 43, 111, 221, 234, 107, 59, 27, 18, 36, 61, 53, 208, 128, 126, 173, 17, 68, 139, 41, 69, 232, 246, 30, 62, 126, 42, 253, 2, 17, 0, 0, 0, 2, 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