Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddefa69d58c9db31c9a2dc868d33b9c86fa603a8a96819a8bed4d861a558c24b

Tx prefix hash: b3b834a05363543096e7b51e4c266f1e7a4b990ad50e0495a0779bc8f01fc9dc
Tx public key: efd2760cf1fa6e57c768b09837870e2489a4d4a68bfb9e782d6782d3097598e7
Timestamp: 1725097250 Timestamp [UCT]: 2024-08-31 09:40:50 Age [y:d:h:m:s]: 01:108:05:28:30
Block: 1099817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335832 RingCT/type: yes/0
Extra: 01efd2760cf1fa6e57c768b09837870e2489a4d4a68bfb9e782d6782d3097598e7021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 912172cc04764af78e001b93167e6f437b0b9cc708da17fb8d87892426e6f5ba 0.600000000000 1575786 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": 1099827, "vin": [ { "gen": { "height": 1099817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "912172cc04764af78e001b93167e6f437b0b9cc708da17fb8d87892426e6f5ba" } } ], "extra": [ 1, 239, 210, 118, 12, 241, 250, 110, 87, 199, 104, 176, 152, 55, 135, 14, 36, 137, 164, 212, 166, 139, 251, 158, 120, 45, 103, 130, 211, 9, 117, 152, 231, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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