Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55fe943729cf0338aa1faf57dd7c95ccccfabfb461622e866018b931155ae232

Tx prefix hash: b31b74be0ebcd9ecfd6d05df5f4984bb2b557736e7d85e16be74dfa3493f0585
Tx public key: aaeaf4b2263dd19e28f34b1a342d5f009e9e220f0c411698d9eb54f4a6c277e0
Timestamp: 1681204043 Timestamp [UCT]: 2023-04-11 09:07:23 Age [y:d:h:m:s]: 01:201:09:28:38
Block: 736155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405394 RingCT/type: yes/0
Extra: 01aaeaf4b2263dd19e28f34b1a342d5f009e9e220f0c411698d9eb54f4a6c277e0021100000005b3164c24000000000000000000

1 output(s) for total of 2.232611287000 dcy

stealth address amount amount idx
00: c38bb820f38903e261cf66a189aad1141d9e2512160469a0277b4a1b0edadf93 2.232611287000 1182558 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": 736165, "vin": [ { "gen": { "height": 736155 } } ], "vout": [ { "amount": 2232611287, "target": { "key": "c38bb820f38903e261cf66a189aad1141d9e2512160469a0277b4a1b0edadf93" } } ], "extra": [ 1, 170, 234, 244, 178, 38, 61, 209, 158, 40, 243, 75, 26, 52, 45, 95, 0, 158, 158, 34, 15, 12, 65, 22, 152, 217, 235, 84, 244, 166, 194, 119, 224, 2, 17, 0, 0, 0, 5, 179, 22, 76, 36, 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