Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 839653a7463c33197cf4b074706c22f128316acd7d4f265dca339c3d936f2564

Tx prefix hash: 55673401e78b1b2bcf67a898d35fca41f59969dd91135f6ea5ed7bf0834ed154
Tx public key: cce98341cefa5c06e138ed11aa0ed71ea2e09a721d4028828a03d997ab5631ee
Timestamp: 1697367226 Timestamp [UCT]: 2023-10-15 10:53:46 Age [y:d:h:m:s]: 01:108:21:25:34
Block: 870119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338817 RingCT/type: yes/0
Extra: 01cce98341cefa5c06e138ed11aa0ed71ea2e09a721d4028828a03d997ab5631ee0211000000024b8f5122000000000000000000

1 output(s) for total of 0.803405086000 dcy

stealth address amount amount idx
00: cc17e57d4bf1dea68f2fbcfc9d48da67c65ea546f4176f38184fd2eb6e33bde7 0.803405086000 1324992 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": 870129, "vin": [ { "gen": { "height": 870119 } } ], "vout": [ { "amount": 803405086, "target": { "key": "cc17e57d4bf1dea68f2fbcfc9d48da67c65ea546f4176f38184fd2eb6e33bde7" } } ], "extra": [ 1, 204, 233, 131, 65, 206, 250, 92, 6, 225, 56, 237, 17, 170, 14, 215, 30, 162, 224, 154, 114, 29, 64, 40, 130, 138, 3, 217, 151, 171, 86, 49, 238, 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