Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e827eaec05390f6bbded4bd39a5ab1eb6d57557d3e956cf90735cfdf9c766e7

Tx prefix hash: b0969c0cf7bca0c8c51f352d2f1202bd1441df5c4a185d44963b8d1bc9c85f8f
Tx public key: 0db043c735275578f6fc55b7d2a0c27742cc8406682be6a9b147d21d6119f9eb
Timestamp: 1722274534 Timestamp [UCT]: 2024-07-29 17:35:34 Age [y:d:h:m:s]: 00:242:07:47:29
Block: 1076406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173098 RingCT/type: yes/0
Extra: 010db043c735275578f6fc55b7d2a0c27742cc8406682be6a9b147d21d6119f9eb02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 216c671bdd5c983cb279cc56b5e05176539fc9a45c87edaf0e90fce68d99f1ea 0.600000000000 1548943 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": 1076416, "vin": [ { "gen": { "height": 1076406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "216c671bdd5c983cb279cc56b5e05176539fc9a45c87edaf0e90fce68d99f1ea" } } ], "extra": [ 1, 13, 176, 67, 199, 53, 39, 85, 120, 246, 252, 85, 183, 210, 160, 194, 119, 66, 204, 132, 6, 104, 43, 230, 169, 177, 71, 210, 29, 97, 25, 249, 235, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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