Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 324c21d76f9cb9226c03bd71804bc590f8467b8b50f0c97cbfaf52b592c3b6a5

Tx prefix hash: eb29292e3bfcaff96bd06532cd992d7b4a9733d280131c51aad317f9bb386b0b
Tx public key: 1dc27565bd1998ec6fde2aa287fb18dbb32bff7f584fbbd853874256b014712a
Timestamp: 1719804456 Timestamp [UCT]: 2024-07-01 03:27:36 Age [y:d:h:m:s]: 00:279:08:57:43
Block: 1055932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199612 RingCT/type: yes/0
Extra: 011dc27565bd1998ec6fde2aa287fb18dbb32bff7f584fbbd853874256b014712a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad3ae1a3b604a7d434646cb2b15b75c1d5dc634c3ee70f3bf210bebf4685aa72 0.600000000000 1526341 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": 1055942, "vin": [ { "gen": { "height": 1055932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad3ae1a3b604a7d434646cb2b15b75c1d5dc634c3ee70f3bf210bebf4685aa72" } } ], "extra": [ 1, 29, 194, 117, 101, 189, 25, 152, 236, 111, 222, 42, 162, 135, 251, 24, 219, 179, 43, 255, 127, 88, 79, 187, 216, 83, 135, 66, 86, 176, 20, 113, 42, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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