Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8ae12ed255b8f0cb6da79fafa41d7e529364629686cac5dbd0492b9bb923d09

Tx prefix hash: 56ad3601ae3f6590f91e8c81a1cb4bde50465a4c7028a0de1c07e99966041fa1
Tx public key: c1821f1910bddd90b93b8aea8f3ac1bc9a13364030cc99ce05f596e69d96978c
Timestamp: 1733582512 Timestamp [UCT]: 2024-12-07 14:41:52 Age [y:d:h:m:s]: 00:107:02:59:29
Block: 1170061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76346 RingCT/type: yes/0
Extra: 01c1821f1910bddd90b93b8aea8f3ac1bc9a13364030cc99ce05f596e69d96978c021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c0ab893db8a0619fa9ba8dfa1e9d38c8fedc4abbbace461037ed530025d9533 0.600000000000 1655790 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": 1170071, "vin": [ { "gen": { "height": 1170061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c0ab893db8a0619fa9ba8dfa1e9d38c8fedc4abbbace461037ed530025d9533" } } ], "extra": [ 1, 193, 130, 31, 25, 16, 189, 221, 144, 185, 59, 138, 234, 143, 58, 193, 188, 154, 19, 54, 64, 48, 204, 153, 206, 5, 245, 150, 230, 157, 150, 151, 140, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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