Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68f7c16fbfc0d917e31eedc1c5fd4986a8850b7be9ffad9408a76aa2196cb01c

Tx prefix hash: 587d1410e5ed96a2b77b99b165791c3dd93dd4cdc6899aa7a3fd9cdd18868f33
Tx public key: 8bc1a970f4c70f00572d7e2cd951f76a01d503080d3d16d898e9d5cac0dcb9c6
Timestamp: 1713369710 Timestamp [UCT]: 2024-04-17 16:01:50 Age [y:d:h:m:s]: 01:200:08:06:15
Block: 1002583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401823 RingCT/type: yes/0
Extra: 018bc1a970f4c70f00572d7e2cd951f76a01d503080d3d16d898e9d5cac0dcb9c602110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e10f5f40758b8599cab9c72cf563b34e233dd25f97cf14e79e3d423e601421c6 0.600000000000 1463101 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": 1002593, "vin": [ { "gen": { "height": 1002583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e10f5f40758b8599cab9c72cf563b34e233dd25f97cf14e79e3d423e601421c6" } } ], "extra": [ 1, 139, 193, 169, 112, 244, 199, 15, 0, 87, 45, 126, 44, 217, 81, 247, 106, 1, 213, 3, 8, 13, 61, 22, 216, 152, 233, 213, 202, 192, 220, 185, 198, 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