Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 286012649db2cddcdd12c7c435a645901cbc2b9e438aa154008a3933d04a36ea

Tx prefix hash: 6f432975bf8c1f212fc43599521dcbd4873e208659f1d4f852da2cff0ddb4ef6
Tx public key: 16c4842ce8ab0a9d4a54b0e459da5d760db6263f76168b1b0ad53119893d7a9c
Timestamp: 1703897465 Timestamp [UCT]: 2023-12-30 00:51:05 Age [y:d:h:m:s]: 01:100:09:31:29
Block: 924054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332860 RingCT/type: yes/0
Extra: 0116c4842ce8ab0a9d4a54b0e459da5d760db6263f76168b1b0ad53119893d7a9c02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9eb3e19541aea5b4ea3fdb0ca7a4d5202abbca70bcce974e48bb24dd0e2c7532 0.600000000000 1381796 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": 924064, "vin": [ { "gen": { "height": 924054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eb3e19541aea5b4ea3fdb0ca7a4d5202abbca70bcce974e48bb24dd0e2c7532" } } ], "extra": [ 1, 22, 196, 132, 44, 232, 171, 10, 157, 74, 84, 176, 228, 89, 218, 93, 118, 13, 182, 38, 63, 118, 22, 139, 27, 10, 213, 49, 25, 137, 61, 122, 156, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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