Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4162570abd9517f897ede3cbfe65be235e083c93e123c7af6ed3dfa37d43dcc5

Tx prefix hash: 219afa79cbbb860cdf8d3efdb14c965c4eb5a0fe3f161cbe67b59e56b65fc951
Tx public key: 2300de06992cf86a1cee754957f94964811de511f7e1b7daa259a51e1038e68b
Timestamp: 1683831916 Timestamp [UCT]: 2023-05-11 19:05:16 Age [y:d:h:m:s]: 01:342:19:30:06
Block: 757958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506247 RingCT/type: yes/0
Extra: 012300de06992cf86a1cee754957f94964811de511f7e1b7daa259a51e1038e68b02110000000233af99f4000000000000000000

1 output(s) for total of 1.890473936000 dcy

stealth address amount amount idx
00: 384c8ae6ea0ad384fc1877b7fdebf04c2919ccc428e3aab2270f3b5c776c2f09 1.890473936000 1206429 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": 757968, "vin": [ { "gen": { "height": 757958 } } ], "vout": [ { "amount": 1890473936, "target": { "key": "384c8ae6ea0ad384fc1877b7fdebf04c2919ccc428e3aab2270f3b5c776c2f09" } } ], "extra": [ 1, 35, 0, 222, 6, 153, 44, 248, 106, 28, 238, 117, 73, 87, 249, 73, 100, 129, 29, 229, 17, 247, 225, 183, 218, 162, 89, 165, 30, 16, 56, 230, 139, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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