Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7452e88f93b862f53def4ebaa18fb59761329c6820291b2671cdf1d1107759b6

Tx prefix hash: 64a16357d4a9f0cdd97bc40c3024b0d23307acf9f8cfc13a723d2f6fa453f9e7
Tx public key: ecf23d88941857fabf80a9cc4996a3b451fcd500fc0f5d9bb224dbc1d9636202
Timestamp: 1720672141 Timestamp [UCT]: 2024-07-11 04:29:01 Age [y:d:h:m:s]: 00:316:04:05:54
Block: 1063137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225935 RingCT/type: yes/0
Extra: 01ecf23d88941857fabf80a9cc4996a3b451fcd500fc0f5d9bb224dbc1d963620202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ff197a936597877b017673ca5d6b50fc745c1f32ac68527f5b3d47365708c4a 0.600000000000 1533650 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": 1063147, "vin": [ { "gen": { "height": 1063137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ff197a936597877b017673ca5d6b50fc745c1f32ac68527f5b3d47365708c4a" } } ], "extra": [ 1, 236, 242, 61, 136, 148, 24, 87, 250, 191, 128, 169, 204, 73, 150, 163, 180, 81, 252, 213, 0, 252, 15, 93, 155, 178, 36, 219, 193, 217, 99, 98, 2, 2, 17, 0, 0, 0, 2, 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