Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a0b5826d767be1c469e65ab5e9aa13967178774524261d6758df048db81045c

Tx prefix hash: 48e2ce225694bc8117db2d927327ee1e7ce6d0d3a9a01ea32b65f73c859fb0a9
Tx public key: 75edc16278ba2cf1dda90429a27bd736ed73355b5fc6c9dbb04c786033c7b4c4
Timestamp: 1709812142 Timestamp [UCT]: 2024-03-07 11:49:02 Age [y:d:h:m:s]: 01:069:07:35:05
Block: 973106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310554 RingCT/type: yes/0
Extra: 0175edc16278ba2cf1dda90429a27bd736ed73355b5fc6c9dbb04c786033c7b4c40211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5249bd026ce6e805af20fa10b2aa2af2354dee89027f024a5f1a8b3896ffa4f 0.600000000000 1433037 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": 973116, "vin": [ { "gen": { "height": 973106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5249bd026ce6e805af20fa10b2aa2af2354dee89027f024a5f1a8b3896ffa4f" } } ], "extra": [ 1, 117, 237, 193, 98, 120, 186, 44, 241, 221, 169, 4, 41, 162, 123, 215, 54, 237, 115, 53, 91, 95, 198, 201, 219, 176, 76, 120, 96, 51, 199, 180, 196, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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