Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8eca2961571e49b488f2943c8c6d39f71c33d0f8e60b4fded08203a7eebc3cfe

Tx prefix hash: 7b6c93182832c37fd8bc33529c0490ee5c63ab9e12876aa250abd774bd127d6b
Tx public key: f19b65cbd09162b7d925adddb4443217fd96bfe4cff5e8194a12576e436a91e5
Timestamp: 1733238934 Timestamp [UCT]: 2024-12-03 15:15:34 Age [y:d:h:m:s]: 00:335:15:12:52
Block: 1167216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237388 RingCT/type: yes/0
Extra: 01f19b65cbd09162b7d925adddb4443217fd96bfe4cff5e8194a12576e436a91e5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3225ef034e4a5a6262621010a0a505768ecacc9d4c00f5870d6ac3e514c5ccf5 0.600000000000 1652911 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": 1167226, "vin": [ { "gen": { "height": 1167216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3225ef034e4a5a6262621010a0a505768ecacc9d4c00f5870d6ac3e514c5ccf5" } } ], "extra": [ 1, 241, 155, 101, 203, 208, 145, 98, 183, 217, 37, 173, 221, 180, 68, 50, 23, 253, 150, 191, 228, 207, 245, 232, 25, 74, 18, 87, 110, 67, 106, 145, 229, 2, 17, 0, 0, 0, 2, 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