Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb8696f0ea18b6349c839aee0a2bf6766568680e9f0d00385cd267505c8b64a9

Tx prefix hash: df5532a62c3bd393ea805d811adf2dcc5333b1472ce5726920c34007b80c741d
Tx public key: 3e82e8c763337e591f1bdb2ca288b437e5b4dc4ceabca1ff4f2f7d29aca84f7a
Timestamp: 1681108239 Timestamp [UCT]: 2023-04-10 06:30:39 Age [y:d:h:m:s]: 02:000:11:58:28
Block: 735355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522520 RingCT/type: yes/0
Extra: 013e82e8c763337e591f1bdb2ca288b437e5b4dc4ceabca1ff4f2f7d29aca84f7a021100000001e6d27f9c000000000000000000

1 output(s) for total of 2.246279787000 dcy

stealth address amount amount idx
00: 912ec7ea8ac69f8154e506379ea79a6a64868179d37a134748afa82a8bd6aecb 2.246279787000 1181670 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": 735365, "vin": [ { "gen": { "height": 735355 } } ], "vout": [ { "amount": 2246279787, "target": { "key": "912ec7ea8ac69f8154e506379ea79a6a64868179d37a134748afa82a8bd6aecb" } } ], "extra": [ 1, 62, 130, 232, 199, 99, 51, 126, 89, 31, 27, 219, 44, 162, 136, 180, 55, 229, 180, 220, 76, 234, 188, 161, 255, 79, 47, 125, 41, 172, 168, 79, 122, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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